Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef371cd67520f282d896dd0ff7a4018a78fd61743fed3e4f1e7b3ad2aa2bb86d

Tx prefix hash: 2a79ba50517099e99d542f772dbedd6267b1550df4d8cc0b9b7f99cf4f4e36a8
Tx public key: 460598d23a84c517bf7db920714cbdecbf9b2c67eba184b99052819727f1e045
Timestamp: 1766261079 Timestamp [UCT]: 2025-12-20 20:04:39 Age [y:d:h:m:s]: 00:001:00:46:08
Block: 1437950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 727 RingCT/type: yes/0
Extra: 01460598d23a84c517bf7db920714cbdecbf9b2c67eba184b99052819727f1e045021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd9e77bb426943bfad5438826865637b2ae25479921e62c3e0be72cb1abf3dbe 0.600000000000 1926763 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": 1437960, "vin": [ { "gen": { "height": 1437950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd9e77bb426943bfad5438826865637b2ae25479921e62c3e0be72cb1abf3dbe" } } ], "extra": [ 1, 70, 5, 152, 210, 58, 132, 197, 23, 191, 125, 185, 32, 113, 76, 189, 236, 191, 155, 44, 103, 235, 161, 132, 185, 144, 82, 129, 151, 39, 241, 224, 69, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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