Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 321ae0a8ef4e79d0086068f4c02e8ec98ee6db822bb08367d593bff1433071d2

Tx prefix hash: b566d21def5346c3ed58d2ebadde3ec9957668b645999f9cd1fbe0374cb2f029
Tx public key: 3c20e329e57107bf628f63319acb521153c91c8d51430f3839e1a2e87c6729f7
Timestamp: 1577660092 Timestamp [UCT]: 2019-12-29 22:54:52 Age [y:d:h:m:s]: 05:307:13:03:27
Block: 34592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367321 RingCT/type: yes/0
Extra: 013c20e329e57107bf628f63319acb521153c91c8d51430f3839e1a2e87c6729f70211000000028a2ee0d9000000000000000000

1 output(s) for total of 471.393076631000 dcy

stealth address amount amount idx
00: 1aec24bf5140b83973a846150b0b5a71f86636a1797dbf79de26dca400cfefe4 471.393076631000 58252 of 0

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": 34602, "vin": [ { "gen": { "height": 34592 } } ], "vout": [ { "amount": 471393076631, "target": { "key": "1aec24bf5140b83973a846150b0b5a71f86636a1797dbf79de26dca400cfefe4" } } ], "extra": [ 1, 60, 32, 227, 41, 229, 113, 7, 191, 98, 143, 99, 49, 154, 203, 82, 17, 83, 201, 28, 141, 81, 67, 15, 56, 57, 225, 162, 232, 124, 103, 41, 247, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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