Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 983eba76e460c1871af62dfbb4d8a17a1173205f7bfc3f2f80f8951bbe85b389

Tx prefix hash: 3c04c397e2190e5cc0fe2c7c918b93036e184724344934ab3e8a04b67f421838
Tx public key: cf9c0aa3efc0890fa9020daaf4aeea710ff810e45cdeca2cb164798852aae765
Timestamp: 1712635498 Timestamp [UCT]: 2024-04-09 04:04:58 Age [y:d:h:m:s]: 01:276:11:05:27
Block: 996476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456367 RingCT/type: yes/0
Extra: 01cf9c0aa3efc0890fa9020daaf4aeea710ff810e45cdeca2cb164798852aae7650211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd8c7acacadcb49bb1a42b6491855a0514c16a66e3a256e2db5889b8c0ab1604 0.600000000000 1456894 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": 996486, "vin": [ { "gen": { "height": 996476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd8c7acacadcb49bb1a42b6491855a0514c16a66e3a256e2db5889b8c0ab1604" } } ], "extra": [ 1, 207, 156, 10, 163, 239, 192, 137, 15, 169, 2, 13, 170, 244, 174, 234, 113, 15, 248, 16, 228, 92, 222, 202, 44, 177, 100, 121, 136, 82, 170, 231, 101, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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