Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54158ba24c5fa4cb554e91981c12baa9fbe361584cac250938338983d75f89cd

Tx prefix hash: cd38922b4f5e8814b91b0d8c33a4e5621271b21481429eb369e59dc19c5a803d
Tx public key: af8a8808db5a67ca58c96d6c99b65a74f10ab548f6cac02b77941f8c0dbf88aa
Timestamp: 1735336092 Timestamp [UCT]: 2024-12-27 21:48:12 Age [y:d:h:m:s]: 00:085:13:47:17
Block: 1184570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60955 RingCT/type: yes/0
Extra: 01af8a8808db5a67ca58c96d6c99b65a74f10ab548f6cac02b77941f8c0dbf88aa02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 053223c2e76965cf149b9a0e0e802010b5a55e6cc6edcbb63b1405a1b5358087 0.600000000000 1671027 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": 1184580, "vin": [ { "gen": { "height": 1184570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "053223c2e76965cf149b9a0e0e802010b5a55e6cc6edcbb63b1405a1b5358087" } } ], "extra": [ 1, 175, 138, 136, 8, 219, 90, 103, 202, 88, 201, 109, 108, 153, 182, 90, 116, 241, 10, 181, 72, 246, 202, 192, 43, 119, 148, 31, 140, 13, 191, 136, 170, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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