Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87af129c6a529f7d68159d3f8388654ff144f228a3727f756542946a723aac3

Tx prefix hash: 1980fdfe9040ad692b02c171bc4775fa48f37aea61b1feec4582a1ce66dcaa0f
Tx public key: 8c1cf092a470dbd28ac1b8dded9b11d9d6d3c774c6028290b9ff4f445e036dff
Timestamp: 1735268768 Timestamp [UCT]: 2024-12-27 03:06:08 Age [y:d:h:m:s]: 00:085:16:02:22
Block: 1184011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61021 RingCT/type: yes/0
Extra: 018c1cf092a470dbd28ac1b8dded9b11d9d6d3c774c6028290b9ff4f445e036dff021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e834a963cbcd6a9c6fb87c0abb779856ec5777347eb73eb6e909187934b0cc4 0.600000000000 1670462 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": 1184021, "vin": [ { "gen": { "height": 1184011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e834a963cbcd6a9c6fb87c0abb779856ec5777347eb73eb6e909187934b0cc4" } } ], "extra": [ 1, 140, 28, 240, 146, 164, 112, 219, 210, 138, 193, 184, 221, 237, 155, 17, 217, 214, 211, 199, 116, 198, 2, 130, 144, 185, 255, 79, 68, 94, 3, 109, 255, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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