Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7083468ea6804cb76b1b494d5f176581457b1edfe7db116f37149b21caa810f4

Tx prefix hash: cf9a31842f4ab12a45fd4953ad1d562a4a4b0c89c3bdda197bc2d7452449f0b8
Tx public key: f39921dbac7e0cf60a25ff00d3b05eb0d57d7cfa8f3ccd2f4f48dc55fdc29d9f
Timestamp: 1707734946 Timestamp [UCT]: 2024-02-12 10:49:06 Age [y:d:h:m:s]: 00:313:03:14:57
Block: 955863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224213 RingCT/type: yes/0
Extra: 01f39921dbac7e0cf60a25ff00d3b05eb0d57d7cfa8f3ccd2f4f48dc55fdc29d9f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dc6decc6de9c9d792d6e7b54a97b831f9e0b88e2ab412609ac886da3388ca09 0.600000000000 1415163 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": 955873, "vin": [ { "gen": { "height": 955863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dc6decc6de9c9d792d6e7b54a97b831f9e0b88e2ab412609ac886da3388ca09" } } ], "extra": [ 1, 243, 153, 33, 219, 172, 126, 12, 246, 10, 37, 255, 0, 211, 176, 94, 176, 213, 125, 124, 250, 143, 60, 205, 47, 79, 72, 220, 85, 253, 194, 157, 159, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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