Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5d25a2e1562909d2735fd089625015d0ec7c46fae167eea6ab3d88eb28e02b

Tx prefix hash: e6a40a810b263040e436a781e531e58b2d0643fec7461cbeeb099059b5a2e8b7
Tx public key: 82c3496675d86a95866fcab83b21810fbb60e0905123491f7e021228fb3126a3
Timestamp: 1724260642 Timestamp [UCT]: 2024-08-21 17:17:22 Age [y:d:h:m:s]: 00:229:22:58:11
Block: 1092893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164207 RingCT/type: yes/0
Extra: 0182c3496675d86a95866fcab83b21810fbb60e0905123491f7e021228fb3126a3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f04ccfda062c9d1a63aa6ac7d8c845884dcc500a9f758916c80a0d7f3c5f534 0.600000000000 1567728 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": 1092903, "vin": [ { "gen": { "height": 1092893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f04ccfda062c9d1a63aa6ac7d8c845884dcc500a9f758916c80a0d7f3c5f534" } } ], "extra": [ 1, 130, 195, 73, 102, 117, 216, 106, 149, 134, 111, 202, 184, 59, 33, 129, 15, 187, 96, 224, 144, 81, 35, 73, 31, 126, 2, 18, 40, 251, 49, 38, 163, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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