Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84256ffeb79c6fa3f50b9f6bc94e393886bc97c4b90e1dc737afe6f3480e455b

Tx prefix hash: 52fcbcb7c71ac21c4fb8bfc6d51d546581ce80cb13452934e89d42e64418e3f1
Tx public key: 6d30245e03f653498691f176bc742dd1a5cc1ec578aaa7a98d9f46c0794a38cd
Timestamp: 1727209025 Timestamp [UCT]: 2024-09-24 20:17:05 Age [y:d:h:m:s]: 00:109:13:37:22
Block: 1117325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78338 RingCT/type: yes/0
Extra: 016d30245e03f653498691f176bc742dd1a5cc1ec578aaa7a98d9f46c0794a38cd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9c92d2e4a3a99d84a0dc9aa55413c8f9f59dd9fac6093650950b02a4c763d70 0.600000000000 1598122 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": 1117335, "vin": [ { "gen": { "height": 1117325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9c92d2e4a3a99d84a0dc9aa55413c8f9f59dd9fac6093650950b02a4c763d70" } } ], "extra": [ 1, 109, 48, 36, 94, 3, 246, 83, 73, 134, 145, 241, 118, 188, 116, 45, 209, 165, 204, 30, 197, 120, 170, 167, 169, 141, 159, 70, 192, 121, 74, 56, 205, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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