Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632b5e37acd77b67f3ef82735aaed285d32354683fa2315c95da5d040f72a80e

Tx prefix hash: 70a459cd22b292aed8813fc9277aac410c75d4cb21942fe460a3b7fa4e747842
Tx public key: cd8fd815359e126e0be9e43e1c5303320b06a870cdfba331e073df8837fbb747
Timestamp: 1715443173 Timestamp [UCT]: 2024-05-11 15:59:33 Age [y:d:h:m:s]: 00:289:13:17:51
Block: 1019802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206915 RingCT/type: yes/0
Extra: 01cd8fd815359e126e0be9e43e1c5303320b06a870cdfba331e073df8837fbb74702110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f4d8b03bd7a1e5f927575ae6bf2567608b34a6f61ccad50721d07d7d528e97 0.600000000000 1483847 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": 1019812, "vin": [ { "gen": { "height": 1019802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f4d8b03bd7a1e5f927575ae6bf2567608b34a6f61ccad50721d07d7d528e97" } } ], "extra": [ 1, 205, 143, 216, 21, 53, 158, 18, 110, 11, 233, 228, 62, 28, 83, 3, 50, 11, 6, 168, 112, 205, 251, 163, 49, 224, 115, 223, 136, 55, 251, 183, 71, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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