Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0360a3c34eb16601984942704f8f06e2e15db6b5333884dbf4bd0f8c22c45b06

Tx prefix hash: 3a4a912e8e7c17430aafe888272d7421841e144df8b157fe9d946c157383b2b2
Tx public key: f988d9512499818427e08c3594ff72f75c5b023afc15e87cb1cd3731fca1c01e
Timestamp: 1748113842 Timestamp [UCT]: 2025-05-24 19:10:42 Age [y:d:h:m:s]: 00:170:00:35:00
Block: 1290091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119207 RingCT/type: yes/0
Extra: 01f988d9512499818427e08c3594ff72f75c5b023afc15e87cb1cd3731fca1c01e021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575b4a924e445f9aaca91344cca228a3760d6c3f76141f9a5cb8535f99695dd4 0.600000000000 1777560 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": 1290101, "vin": [ { "gen": { "height": 1290091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575b4a924e445f9aaca91344cca228a3760d6c3f76141f9a5cb8535f99695dd4" } } ], "extra": [ 1, 249, 136, 217, 81, 36, 153, 129, 132, 39, 224, 140, 53, 148, 255, 114, 247, 92, 91, 2, 58, 252, 21, 232, 124, 177, 205, 55, 49, 252, 161, 192, 30, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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