Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 084cae5c975753f2bd41f8f0e0ee9de585c714d7d5cbe51508097e89e2e9593d

Tx prefix hash: 1cd647259901fbbb0a9372fabaf033579838e4c10a6d05b65d6890bdbb93fdb9
Tx public key: 92ff5a52937eb7e99065d1a4ba616579980e6d534ca9a3ad9751c6e352b75511
Timestamp: 1758825038 Timestamp [UCT]: 2025-09-25 18:30:38 Age [y:d:h:m:s]: 00:012:04:15:55
Block: 1376326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8701 RingCT/type: yes/0
Extra: 0192ff5a52937eb7e99065d1a4ba616579980e6d534ca9a3ad9751c6e352b75511021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e3bc87dafea247f9229982aabc76c2624f252c7d836dfe362875b9c60336ad3 0.600000000000 1864417 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": 1376336, "vin": [ { "gen": { "height": 1376326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e3bc87dafea247f9229982aabc76c2624f252c7d836dfe362875b9c60336ad3" } } ], "extra": [ 1, 146, 255, 90, 82, 147, 126, 183, 233, 144, 101, 209, 164, 186, 97, 101, 121, 152, 14, 109, 83, 76, 169, 163, 173, 151, 81, 198, 227, 82, 183, 85, 17, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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