Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0311ce21a6ad94415c83dfac9219e790e292e46f350aee425ae464def171733c

Tx prefix hash: df14dc4f630b364aa9c71053daa7a2e7cec88c0c82f83da781869c7bff511d0e
Tx public key: 6560a0d8578a21b64e84fa46aaec702a273c39be63539b1e0300c77006a5bb8a
Timestamp: 1724635745 Timestamp [UCT]: 2024-08-26 01:29:05 Age [y:d:h:m:s]: 00:277:04:01:21
Block: 1095973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198006 RingCT/type: yes/0
Extra: 016560a0d8578a21b64e84fa46aaec702a273c39be63539b1e0300c77006a5bb8a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e1d9850045b1afeb06a01ef34bd9813ece6ff92087950f7ac0feeab57c0e077 0.600000000000 1571160 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": 1095983, "vin": [ { "gen": { "height": 1095973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e1d9850045b1afeb06a01ef34bd9813ece6ff92087950f7ac0feeab57c0e077" } } ], "extra": [ 1, 101, 96, 160, 216, 87, 138, 33, 182, 78, 132, 250, 70, 170, 236, 112, 42, 39, 60, 57, 190, 99, 83, 155, 30, 3, 0, 199, 112, 6, 165, 187, 138, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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