Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453b262aef09f3091785f29d2125485e1ba5bfd5a52a0574ed33236eb5f43b32

Tx prefix hash: f7b7623fe747f499106055f2fc9e4ee1ef498c061142a458d940cb113c2a7e3e
Tx public key: 438b51e8b68d996f8a5edd37e4e950531fc03cdab9cb1a1f1e0ebea646deb469
Timestamp: 1726809461 Timestamp [UCT]: 2024-09-20 05:17:41 Age [y:d:h:m:s]: 00:124:11:49:41
Block: 1114011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88973 RingCT/type: yes/0
Extra: 01438b51e8b68d996f8a5edd37e4e950531fc03cdab9cb1a1f1e0ebea646deb4690211000000022c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f2315db3183eff2d6a6c1debf0839975d8d45b39e9af68564debb8f7a9d831f 0.600000000000 1593808 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": 1114021, "vin": [ { "gen": { "height": 1114011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f2315db3183eff2d6a6c1debf0839975d8d45b39e9af68564debb8f7a9d831f" } } ], "extra": [ 1, 67, 139, 81, 232, 182, 141, 153, 111, 138, 94, 221, 55, 228, 233, 80, 83, 31, 192, 60, 218, 185, 203, 26, 31, 30, 14, 190, 166, 70, 222, 180, 105, 2, 17, 0, 0, 0, 2, 44, 58, 52, 220, 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