Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1fa50e5a3773db0c5c64f2ec59a6c99274425c7e38fbe670e6f557f510f88fa2

Tx prefix hash: 836cff81424ca9980e3ad0762d7e88969a1ee86075bbaa245792a07cc73ab2fe
Tx public key: c634053a51219e90dd00cc0d201f78fa4b6f668f64a17b5556aea5f564e155b4
Timestamp: 1706241374 Timestamp [UCT]: 2024-01-26 03:56:14 Age [y:d:h:m:s]: 01:030:17:51:36
Block: 943461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283035 RingCT/type: yes/0
Extra: 01c634053a51219e90dd00cc0d201f78fa4b6f668f64a17b5556aea5f564e155b402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7370c1ade5867d294c3ead134479bdc4fb5612dca8dfffb415b048e713864208 0.600000000000 1401667 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 943471, "vin": [ { "gen": { "height": 943461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7370c1ade5867d294c3ead134479bdc4fb5612dca8dfffb415b048e713864208" } } ], "extra": [ 1, 198, 52, 5, 58, 81, 33, 158, 144, 221, 0, 204, 13, 32, 31, 120, 250, 75, 111, 102, 143, 100, 161, 123, 85, 86, 174, 165, 245, 100, 225, 85, 180, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8