Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b74455001d18c19c740a235836e1246ca5ee953d92a9d29644e8b33d11b6229

Tx prefix hash: fa8ecbb694176a1101b279f196ece01db19b478efb2202a8a22709014741dba9
Tx public key: d3e9db314d3550654481083bda1c710aec9b7ab7be61ddd2df6c6f7357f434b0
Timestamp: 1733590132 Timestamp [UCT]: 2024-12-07 16:48:52 Age [y:d:h:m:s]: 00:130:10:36:08
Block: 1170120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93031 RingCT/type: yes/0
Extra: 01d3e9db314d3550654481083bda1c710aec9b7ab7be61ddd2df6c6f7357f434b0021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c9a5f2bcf9af5cf3a6ea21178263c03cfc8e51342b7e0116534800d1a5e887b 0.600000000000 1655849 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": 1170130, "vin": [ { "gen": { "height": 1170120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c9a5f2bcf9af5cf3a6ea21178263c03cfc8e51342b7e0116534800d1a5e887b" } } ], "extra": [ 1, 211, 233, 219, 49, 77, 53, 80, 101, 68, 129, 8, 59, 218, 28, 113, 10, 236, 155, 122, 183, 190, 97, 221, 210, 223, 108, 111, 115, 87, 244, 52, 176, 2, 17, 0, 0, 0, 6, 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