Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d88d1f6d2b041da3b0460d7e7947bae53dbf6a2a4f4f7b07bf25b566f24a14

Tx prefix hash: c616d1b4e85308f809eea84d250d570aba64b9bd35d111e786a5ec8c68456db8
Tx public key: e1cfb6ca46ab4b362cc4ca86f4854dff322e811a53c12dabf4f2403d17abcd93
Timestamp: 1694352424 Timestamp [UCT]: 2023-09-10 13:27:04 Age [y:d:h:m:s]: 01:172:04:51:32
Block: 845103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384151 RingCT/type: yes/0
Extra: 01e1cfb6ca46ab4b362cc4ca86f4854dff322e811a53c12dabf4f2403d17abcd9302110000000675e3f0e9000000000000000000

1 output(s) for total of 0.972350867000 dcy

stealth address amount amount idx
00: d2c5b5e55ad848cccd7a5d6155ae4e5d5f464306c488ebdd0555029533caa8d7 0.972350867000 1298459 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": 845113, "vin": [ { "gen": { "height": 845103 } } ], "vout": [ { "amount": 972350867, "target": { "key": "d2c5b5e55ad848cccd7a5d6155ae4e5d5f464306c488ebdd0555029533caa8d7" } } ], "extra": [ 1, 225, 207, 182, 202, 70, 171, 75, 54, 44, 196, 202, 134, 244, 133, 77, 255, 50, 46, 129, 26, 83, 193, 45, 171, 244, 242, 64, 61, 23, 171, 205, 147, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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