Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d7fe70bb29c6b34bb3d174fca050967f220d5e61f517c96cc1f40692b8cc36

Tx prefix hash: a300c0da677b7a7edf30a6df6a119cb968970f6439ee1fb281581dcb1715d3b8
Tx public key: 8869cd21554ee55b5a0350c14780630f9cbf245024b943cb7c554bb25b1a5fcb
Timestamp: 1703263551 Timestamp [UCT]: 2023-12-22 16:45:51 Age [y:d:h:m:s]: 01:145:19:29:50
Block: 918806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365351 RingCT/type: yes/0
Extra: 018869cd21554ee55b5a0350c14780630f9cbf245024b943cb7c554bb25b1a5fcb02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9584c2ba4f23fd560902b65ecbbbdc91331b907e8438cb4ca8b2c045ac99fcfd 0.600000000000 1376464 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": 918816, "vin": [ { "gen": { "height": 918806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9584c2ba4f23fd560902b65ecbbbdc91331b907e8438cb4ca8b2c045ac99fcfd" } } ], "extra": [ 1, 136, 105, 205, 33, 85, 78, 229, 91, 90, 3, 80, 193, 71, 128, 99, 15, 156, 191, 36, 80, 36, 185, 67, 203, 124, 85, 75, 178, 91, 26, 95, 203, 2, 17, 0, 0, 0, 5, 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