Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5112d10c2e627c4dc1496d0e59f7dcb7bf4feb20f2f429037dc8cc427ebbb122

Tx prefix hash: b408fada9794d546506bce3e7c618f2709f39b1c98772be50a192904e8063895
Tx public key: 55519463433b504a8d7dde883194b64ddfb979f3a5a1e5adcba93e1ff7fcc068
Timestamp: 1764613203 Timestamp [UCT]: 2025-12-01 18:20:03 Age [y:d:h:m:s]: 00:021:06:26:41
Block: 1424287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15229 RingCT/type: yes/0
Extra: 0155519463433b504a8d7dde883194b64ddfb979f3a5a1e5adcba93e1ff7fcc06802110000000343b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23dbf0a605b506d19ee931af1af6f7442f0fa16e3a950b704a06484a4c67d2a4 0.600000000000 1912918 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": 1424297, "vin": [ { "gen": { "height": 1424287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23dbf0a605b506d19ee931af1af6f7442f0fa16e3a950b704a06484a4c67d2a4" } } ], "extra": [ 1, 85, 81, 148, 99, 67, 59, 80, 74, 141, 125, 222, 136, 49, 148, 182, 77, 223, 185, 121, 243, 165, 161, 229, 173, 203, 169, 62, 31, 247, 252, 192, 104, 2, 17, 0, 0, 0, 3, 67, 181, 4, 113, 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