Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5154ebf55f6259016126574f772001ed4e4646ac5b241e13a9304c48cddc1341

Tx prefix hash: fa8023fb27e0311f9b66ed1dcbc335ccd4893bb1c83a26fca0d10d84cc4de86c
Tx public key: a2a68d60815285d6f0a9f7a99faf78fbdbc7f09e196cdcb08d7eda1591502a19
Timestamp: 1705379559 Timestamp [UCT]: 2024-01-16 04:32:39 Age [y:d:h:m:s]: 01:308:19:56:44
Block: 936320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479563 RingCT/type: yes/0
Extra: 01a2a68d60815285d6f0a9f7a99faf78fbdbc7f09e196cdcb08d7eda1591502a190211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c13e1d384e30dea6cb8c0b3207a8d2073006bb2cddb611927e4c9e7ba9410d5b 0.600000000000 1394344 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": 936330, "vin": [ { "gen": { "height": 936320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c13e1d384e30dea6cb8c0b3207a8d2073006bb2cddb611927e4c9e7ba9410d5b" } } ], "extra": [ 1, 162, 166, 141, 96, 129, 82, 133, 214, 240, 169, 247, 169, 159, 175, 120, 251, 219, 199, 240, 158, 25, 108, 220, 176, 141, 126, 218, 21, 145, 80, 42, 25, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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