Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97d857a4ffe462ec97fa3fd58856f70ba4ec6fb303c9d1610fcac3ab81786b60

Tx prefix hash: 5756010a37a7aff51934f7338a305d7cf39fbf851e76a7401101707b98f2f72e
Tx public key: 1ffaee35e82f2a018cdc8b6a30174b36302ef95b21e02d3b7997410c3c6dc133
Timestamp: 1699529985 Timestamp [UCT]: 2023-11-09 11:39:45 Age [y:d:h:m:s]: 01:129:18:58:38
Block: 887857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353940 RingCT/type: yes/0
Extra: 011ffaee35e82f2a018cdc8b6a30174b36302ef95b21e02d3b7997410c3c6dc13302110000000e33af99f4000000000000000000

1 output(s) for total of 0.701715700000 dcy

stealth address amount amount idx
00: 24db9f18c958066143d575b9b9d8dbab9be4cfb35b68195c0b856c8b564a45f4 0.701715700000 1343764 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": 887867, "vin": [ { "gen": { "height": 887857 } } ], "vout": [ { "amount": 701715700, "target": { "key": "24db9f18c958066143d575b9b9d8dbab9be4cfb35b68195c0b856c8b564a45f4" } } ], "extra": [ 1, 31, 250, 238, 53, 232, 47, 42, 1, 140, 220, 139, 106, 48, 23, 75, 54, 48, 46, 249, 91, 33, 224, 45, 59, 121, 151, 65, 12, 60, 109, 193, 51, 2, 17, 0, 0, 0, 14, 51, 175, 153, 244, 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