Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c545200ef3bb3e135ff6fe50fd09d310939e3992312f7cad8b8c41982049f782

Tx prefix hash: 408222144a8804265acc9e3cdf20d724e5e3e36805e3d736944239eb02865fbc
Tx public key: 0e9c9428b29124f99b6da8e1d470d84911ab07e6a642d94c9b38b798fa4fc6c2
Timestamp: 1749374811 Timestamp [UCT]: 2025-06-08 09:26:51 Age [y:d:h:m:s]: 00:155:12:07:31
Block: 1300539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108812 RingCT/type: yes/0
Extra: 010e9c9428b29124f99b6da8e1d470d84911ab07e6a642d94c9b38b798fa4fc6c2021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa4010854bc9082031d91aa477b9fb2661c8bb767ee885e1cb55b822c1e79b56 0.600000000000 1788088 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": 1300549, "vin": [ { "gen": { "height": 1300539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa4010854bc9082031d91aa477b9fb2661c8bb767ee885e1cb55b822c1e79b56" } } ], "extra": [ 1, 14, 156, 148, 40, 178, 145, 36, 249, 155, 109, 168, 225, 212, 112, 216, 73, 17, 171, 7, 230, 166, 66, 217, 76, 155, 56, 183, 152, 250, 79, 198, 194, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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