Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6217e54ae35730bc8bbde7d009f3a1873452f5d5cf8cb4a8370974aacc0b09da

Tx prefix hash: 62c23ee47517bc8bf9da0c31c098e9948e8af503b0d62faa6f658260d6e1ac62
Tx public key: 4431cd02ff921e4f181e859635aa1add9a5f9f38bf9a15d0c5baaccad42d963a
Timestamp: 1763720897 Timestamp [UCT]: 2025-11-21 10:28:17 Age [y:d:h:m:s]: 00:006:02:55:40
Block: 1416886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4393 RingCT/type: yes/0
Extra: 014431cd02ff921e4f181e859635aa1add9a5f9f38bf9a15d0c5baaccad42d963a02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba189d5bf3e276c89d8dfd3064262e6be585a4cc5085315a79f03457822270da 0.600000000000 1905407 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": 1416896, "vin": [ { "gen": { "height": 1416886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba189d5bf3e276c89d8dfd3064262e6be585a4cc5085315a79f03457822270da" } } ], "extra": [ 1, 68, 49, 205, 2, 255, 146, 30, 79, 24, 30, 133, 150, 53, 170, 26, 221, 154, 95, 159, 56, 191, 154, 21, 208, 197, 186, 172, 202, 212, 45, 150, 58, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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