Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77b713d298a11600b689218661957c29d07489494a7a42f47becbedb382ba161

Tx prefix hash: e21dbe01af263a7057826b361ad61078d801ea8a2659a7efb23313bee7b385bf
Tx public key: 82d425d6e198ae3599308095b286ec20e8b3d5602a5bc8521253e72595c22ab4
Timestamp: 1710420950 Timestamp [UCT]: 2024-03-14 12:55:50 Age [y:d:h:m:s]: 00:345:20:37:17
Block: 978157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247250 RingCT/type: yes/0
Extra: 0182d425d6e198ae3599308095b286ec20e8b3d5602a5bc8521253e72595c22ab402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d3f7a612e031232d2f7b6e819b65099b055a458b2e0c912d9f38d3b3f42214d 0.600000000000 1438174 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": 978167, "vin": [ { "gen": { "height": 978157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d3f7a612e031232d2f7b6e819b65099b055a458b2e0c912d9f38d3b3f42214d" } } ], "extra": [ 1, 130, 212, 37, 214, 225, 152, 174, 53, 153, 48, 128, 149, 178, 134, 236, 32, 232, 179, 213, 96, 42, 91, 200, 82, 18, 83, 231, 37, 149, 194, 42, 180, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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