Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6c52d0a71023da021ce344cdf02725f1c584a921ec0a4f193277f195387709f

Tx prefix hash: 55933cf0156d3d69020b96ddc6d31f98008cdea48ffc8ea2a8415d2539ecca83
Tx public key: 933a481c29736d9b015fdfd872602e4b8c04a6fd623111402426215b9dff6b04
Timestamp: 1744483436 Timestamp [UCT]: 2025-04-12 18:43:56 Age [y:d:h:m:s]: 00:213:14:31:17
Block: 1260031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150379 RingCT/type: yes/0
Extra: 01933a481c29736d9b015fdfd872602e4b8c04a6fd623111402426215b9dff6b040211000000076c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27b5436f850c1f924cd68318ccb74dcdbb8108ab8c9dee4bedf33d537f19dae 0.600000000000 1747182 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": 1260041, "vin": [ { "gen": { "height": 1260031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27b5436f850c1f924cd68318ccb74dcdbb8108ab8c9dee4bedf33d537f19dae" } } ], "extra": [ 1, 147, 58, 72, 28, 41, 115, 109, 155, 1, 95, 223, 216, 114, 96, 46, 75, 140, 4, 166, 253, 98, 49, 17, 64, 36, 38, 33, 91, 157, 255, 107, 4, 2, 17, 0, 0, 0, 7, 108, 152, 170, 61, 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