Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bdc57db64e9d3753a6994216c6ae1e698573ecaf3d1086493d462d28f2af92f

Tx prefix hash: 9a6af40d4507413353ae946f0e27056a94b12546064300e39efdb42a2c31f708
Tx public key: c106c008e9d83b28f6c3e403f769baeab22cd8e2473e1a083c1662437ea6d200
Timestamp: 1735678932 Timestamp [UCT]: 2024-12-31 21:02:12 Age [y:d:h:m:s]: 00:113:12:09:42
Block: 1187406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80932 RingCT/type: yes/0
Extra: 01c106c008e9d83b28f6c3e403f769baeab22cd8e2473e1a083c1662437ea6d200021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 963556ab683c7af8a0dcc90a3dc596e2edf1c7c66318acff396504219167f507 0.600000000000 1673895 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": 1187416, "vin": [ { "gen": { "height": 1187406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963556ab683c7af8a0dcc90a3dc596e2edf1c7c66318acff396504219167f507" } } ], "extra": [ 1, 193, 6, 192, 8, 233, 216, 59, 40, 246, 195, 228, 3, 247, 105, 186, 234, 178, 44, 216, 226, 71, 62, 26, 8, 60, 22, 98, 67, 126, 166, 210, 0, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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