Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 734549b9eabd6c55c141337f066ebb6ebf50607dd64773bb29de88f5f145872a

Tx prefix hash: c94ee5c6ff3b1d8dd1fd19d0ac4da53ddf72f8ded4a2843659d29207f032c4d9
Tx public key: 6213c7b6dd9ffc7778e1bc4e7d2c6cfbd633192238b6edc610f824ab81c4adb3
Timestamp: 1713508277 Timestamp [UCT]: 2024-04-19 06:31:17 Age [y:d:h:m:s]: 00:311:23:26:04
Block: 1003733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223002 RingCT/type: yes/0
Extra: 016213c7b6dd9ffc7778e1bc4e7d2c6cfbd633192238b6edc610f824ab81c4adb302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a6509759aef3907b47728bbe6338e881fec734caefdf6c357267e6e1cbdf23 0.600000000000 1464275 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": 1003743, "vin": [ { "gen": { "height": 1003733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a6509759aef3907b47728bbe6338e881fec734caefdf6c357267e6e1cbdf23" } } ], "extra": [ 1, 98, 19, 199, 182, 221, 159, 252, 119, 120, 225, 188, 78, 125, 44, 108, 251, 214, 51, 25, 34, 56, 182, 237, 198, 16, 248, 36, 171, 129, 196, 173, 179, 2, 17, 0, 0, 0, 4, 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