Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf0acab7c1b8fefbca0499ab8f099c4c6e3bb29a2b205721c8dfb5dec9ca938

Tx prefix hash: eaf3ced5cdd2f3d90741fe157df1e15468917c4d7ccf7846c1867e7ea3bd1008
Tx public key: bd29fbe882e6bd85623535baa119d98105759f601182e640793d26e225de2f77
Timestamp: 1738262478 Timestamp [UCT]: 2025-01-30 18:41:18 Age [y:d:h:m:s]: 00:320:03:19:26
Block: 1208536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226599 RingCT/type: yes/0
Extra: 01bd29fbe882e6bd85623535baa119d98105759f601182e640793d26e225de2f77021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42b0305cbbfb33884e1acc3bcb37dcd66e942e4aba81be7ef0e817a8c57c432f 0.600000000000 1695269 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": 1208546, "vin": [ { "gen": { "height": 1208536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42b0305cbbfb33884e1acc3bcb37dcd66e942e4aba81be7ef0e817a8c57c432f" } } ], "extra": [ 1, 189, 41, 251, 232, 130, 230, 189, 133, 98, 53, 53, 186, 161, 25, 217, 129, 5, 117, 159, 96, 17, 130, 230, 64, 121, 61, 38, 226, 37, 222, 47, 119, 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