Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abd11528c8d380585be8722a27479cbb5bb709c3e6c8b7eba2ffd0b383e37017

Tx prefix hash: 7ab28a0babbd6ee423eb23aba915d18e08c7a370e29e885b8e124cfe71673094
Tx public key: 33deb5d47cbcf0c7e2c6c3178d80cb62b112deac86e4c8a763b5258de2eb6e58
Timestamp: 1728070683 Timestamp [UCT]: 2024-10-04 19:38:03 Age [y:d:h:m:s]: 00:050:22:23:41
Block: 1124468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36382 RingCT/type: yes/0
Extra: 0133deb5d47cbcf0c7e2c6c3178d80cb62b112deac86e4c8a763b5258de2eb6e5802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f7befc203a2ecf88e145f4e55741aa6c394e1974ebe47335cc1dadf7daead38 0.600000000000 1607095 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": 1124478, "vin": [ { "gen": { "height": 1124468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f7befc203a2ecf88e145f4e55741aa6c394e1974ebe47335cc1dadf7daead38" } } ], "extra": [ 1, 51, 222, 181, 212, 124, 188, 240, 199, 226, 198, 195, 23, 141, 128, 203, 98, 177, 18, 222, 172, 134, 228, 200, 167, 99, 181, 37, 141, 226, 235, 110, 88, 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