Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b886be7f97ea574f5b38bde70e2503f7c1568662bc6a4ce9cea3043d0deafda

Tx prefix hash: 9c10d634ec082a8d7c5700fd4bbd69cc9549e1154d9fa65fa81cca246bdbc363
Tx public key: 190e43b82996c3fd4c7d08a4af262064adfcd68aa0dc48aba8bf23857a4e37ae
Timestamp: 1704137651 Timestamp [UCT]: 2024-01-01 19:34:11 Age [y:d:h:m:s]: 01:017:15:14:34
Block: 926037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273938 RingCT/type: yes/0
Extra: 01190e43b82996c3fd4c7d08a4af262064adfcd68aa0dc48aba8bf23857a4e37ae02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8d27849925ca4b265e29fc735b4a3770c91405cccd177ad1b3be1ba7f307356 0.600000000000 1383809 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": 926047, "vin": [ { "gen": { "height": 926037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8d27849925ca4b265e29fc735b4a3770c91405cccd177ad1b3be1ba7f307356" } } ], "extra": [ 1, 25, 14, 67, 184, 41, 150, 195, 253, 76, 125, 8, 164, 175, 38, 32, 100, 173, 252, 214, 138, 160, 220, 72, 171, 168, 191, 35, 133, 122, 78, 55, 174, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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