Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e8afe05d182e10ceb18d42ca85e7d1ab0999c78c09fb30c57456e1979b80317

Tx prefix hash: 78e6f88f3791dab3012b4eaafb7cc48f1c65a38f8d9c6f550a82374445a0b89c
Tx public key: 031ba8a14ece161b9f2371e7a0d7dc12a93cc66a001e2bf1842542b99bdd649b
Timestamp: 1733724575 Timestamp [UCT]: 2024-12-09 06:09:35 Age [y:d:h:m:s]: 00:142:16:40:41
Block: 1171240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101788 RingCT/type: yes/0
Extra: 01031ba8a14ece161b9f2371e7a0d7dc12a93cc66a001e2bf1842542b99bdd649b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb66787b582e4dda7f51e445a6d51ef076735efb620154e860ddf2c7e5278697 0.600000000000 1656979 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": 1171250, "vin": [ { "gen": { "height": 1171240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb66787b582e4dda7f51e445a6d51ef076735efb620154e860ddf2c7e5278697" } } ], "extra": [ 1, 3, 27, 168, 161, 78, 206, 22, 27, 159, 35, 113, 231, 160, 215, 220, 18, 169, 60, 198, 106, 0, 30, 43, 241, 132, 37, 66, 185, 155, 221, 100, 155, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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