Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a461345cb3772c8a4eb24932477b9aefa6e411c5aba24cbfca21bfea6b08618d

Tx prefix hash: c577e65d437a17935a5e031b56c4b69d0b715de8c53c00c38a9789165462b38f
Tx public key: a8ba66d6d347677f84f016bd163ae02d7d9ec9769ed8e4d55cb3abc4483490b6
Timestamp: 1673529600 Timestamp [UCT]: 2023-01-12 13:20:00 Age [y:d:h:m:s]: 02:095:16:21:22
Block: 673153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590060 RingCT/type: yes/0
Extra: 01a8ba66d6d347677f84f016bd163ae02d7d9ec9769ed8e4d55cb3abc4483490b60211000000038b7b6602000000000000000000

1 output(s) for total of 3.610477347000 dcy

stealth address amount amount idx
00: be2158a09780857faef5b192bf343845962931b2b11cdaedcf7c38ce153dba12 3.610477347000 1114746 of 0

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": 673163, "vin": [ { "gen": { "height": 673153 } } ], "vout": [ { "amount": 3610477347, "target": { "key": "be2158a09780857faef5b192bf343845962931b2b11cdaedcf7c38ce153dba12" } } ], "extra": [ 1, 168, 186, 102, 214, 211, 71, 103, 127, 132, 240, 22, 189, 22, 58, 224, 45, 125, 158, 201, 118, 158, 216, 228, 213, 92, 179, 171, 196, 72, 52, 144, 182, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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