Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3cbe1e0bfdc3da48daa9b5c4154b870fb86ab4a9356b348fa071242fe46427

Tx prefix hash: 4d36444bc7b005508d32de2b2ff99f235d9fe135b957234f156b4cba8f07b012
Tx public key: a1935f7aa5da52a1397890b4b1a8cf7b9e44febbafd09641040f26a019998418
Timestamp: 1723734490 Timestamp [UCT]: 2024-08-15 15:08:10 Age [y:d:h:m:s]: 00:231:10:24:24
Block: 1088518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165275 RingCT/type: yes/0
Extra: 01a1935f7aa5da52a1397890b4b1a8cf7b9e44febbafd09641040f26a019998418021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99b3fa5117cc667c8d59e67c7e88717a34a6e434251fe526ad01ce3d48ec1d38 0.600000000000 1563135 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": 1088528, "vin": [ { "gen": { "height": 1088518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99b3fa5117cc667c8d59e67c7e88717a34a6e434251fe526ad01ce3d48ec1d38" } } ], "extra": [ 1, 161, 147, 95, 122, 165, 218, 82, 161, 57, 120, 144, 180, 177, 168, 207, 123, 158, 68, 254, 187, 175, 208, 150, 65, 4, 15, 38, 160, 25, 153, 132, 24, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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