Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 671c6fd5bea948cb6be497cc3f7e9564723a4a0dce218114f26dcaf9ee874279

Tx prefix hash: 52f2aa5252401ccc260443dc4dcf1ec538a907b6c8ed7b2f0ab19fdc20b83c91
Tx public key: 6d416adc9893377c26e21ffcf5408d375abecf42c8a6fb3efcdf96ec986d5cb4
Timestamp: 1763463542 Timestamp [UCT]: 2025-11-18 10:59:02 Age [y:d:h:m:s]: 00:009:18:53:53
Block: 1414766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7006 RingCT/type: yes/0
Extra: 016d416adc9893377c26e21ffcf5408d375abecf42c8a6fb3efcdf96ec986d5cb4021100000002defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db1fac134c4e09f105651002e263348b7e525279e73cdfd85e8dfefd05f4306 0.600000000000 1903257 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": 1414776, "vin": [ { "gen": { "height": 1414766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db1fac134c4e09f105651002e263348b7e525279e73cdfd85e8dfefd05f4306" } } ], "extra": [ 1, 109, 65, 106, 220, 152, 147, 55, 124, 38, 226, 31, 252, 245, 64, 141, 55, 90, 190, 207, 66, 200, 166, 251, 62, 252, 223, 150, 236, 152, 109, 92, 180, 2, 17, 0, 0, 0, 2, 222, 251, 143, 24, 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