Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9882415b0029270aced173037ff8ce0014b1979eed94c5b1bf5d3e3d63d521b

Tx prefix hash: f273f05b77ea75453cfb4a11ff51f69fa884803785163023e74327df3383bc78
Tx public key: 1a697f226cab40d03cf63983b716f7a20fdd74092df9a6aa8d52095ef14c829c
Timestamp: 1720037713 Timestamp [UCT]: 2024-07-03 20:15:13 Age [y:d:h:m:s]: 01:128:23:25:40
Block: 1057857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350726 RingCT/type: yes/0
Extra: 011a697f226cab40d03cf63983b716f7a20fdd74092df9a6aa8d52095ef14c829c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de01a68dd2a51c5b623e1ce5e0a5fbf9110b3ea4453d60d25ecedbbc2e2226cf 0.600000000000 1528300 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": 1057867, "vin": [ { "gen": { "height": 1057857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de01a68dd2a51c5b623e1ce5e0a5fbf9110b3ea4453d60d25ecedbbc2e2226cf" } } ], "extra": [ 1, 26, 105, 127, 34, 108, 171, 64, 208, 60, 246, 57, 131, 183, 22, 247, 162, 15, 221, 116, 9, 45, 249, 166, 170, 141, 82, 9, 94, 241, 76, 130, 156, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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