Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f61f9cc8bdc2393399d47568d0541197102c5157afb7d11290a83c8cb734518

Tx prefix hash: 190a63e755a6d330c506776b5fc3d25ef99717f360a8cbb354d0b195560ae6e1
Tx public key: f855e74d74d2e95f58dd9a5da5066fea3464e57e1273de424224978cea44f0c7
Timestamp: 1661351203 Timestamp [UCT]: 2022-08-24 14:26:43 Age [y:d:h:m:s]: 02:174:00:13:10
Block: 572856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645575 RingCT/type: yes/0
Extra: 01f855e74d74d2e95f58dd9a5da5066fea3464e57e1273de424224978cea44f0c702110000002afaf35c9c000000000000000000

1 output(s) for total of 7.760511860000 dcy

stealth address amount amount idx
00: 7abfae377a9f5d38f8c9201719eb35ed90e49f805d29bc346f29cc159a9e3b2f 7.760511860000 1006128 of 0

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": 572866, "vin": [ { "gen": { "height": 572856 } } ], "vout": [ { "amount": 7760511860, "target": { "key": "7abfae377a9f5d38f8c9201719eb35ed90e49f805d29bc346f29cc159a9e3b2f" } } ], "extra": [ 1, 248, 85, 231, 77, 116, 210, 233, 95, 88, 221, 154, 93, 165, 6, 111, 234, 52, 100, 229, 126, 18, 115, 222, 66, 66, 36, 151, 140, 234, 68, 240, 199, 2, 17, 0, 0, 0, 42, 250, 243, 92, 156, 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