Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28d22c0f8550f507fd8c806818b2844a998c4f17738da6706b551446cdb7005c

Tx prefix hash: d53c8586f094078856d9dfdc8c6d627e0554af1a461e8609122cc7b7eb4ffe64
Tx public key: e934f414545bcadbcb7b401ee8a8637f0834fbb747a3d2e9621ef6027dc5cc3b
Timestamp: 1641681629 Timestamp [UCT]: 2022-01-08 22:40:29 Age [y:d:h:m:s]: 03:296:04:23:15
Block: 413303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 988347 RingCT/type: yes/0
Extra: 01e934f414545bcadbcb7b401ee8a8637f0834fbb747a3d2e9621ef6027dc5cc3b021100000026e2bb00ee000000000000000000

1 output(s) for total of 26.215365837000 dcy

stealth address amount amount idx
00: 63d21babe07ff1b4ac464827ca77ed75cbe1220734f35490a7f55192d21d4fa7 26.215365837000 817931 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": 413313, "vin": [ { "gen": { "height": 413303 } } ], "vout": [ { "amount": 26215365837, "target": { "key": "63d21babe07ff1b4ac464827ca77ed75cbe1220734f35490a7f55192d21d4fa7" } } ], "extra": [ 1, 233, 52, 244, 20, 84, 91, 202, 219, 203, 123, 64, 30, 232, 168, 99, 127, 8, 52, 251, 183, 71, 163, 210, 233, 98, 30, 246, 2, 125, 197, 204, 59, 2, 17, 0, 0, 0, 38, 226, 187, 0, 238, 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