Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e39603ba24abbcbc82d8e9c06e83bf2a8771268675510db3f6dda1dc04657ba

Tx prefix hash: 6f14fd5e8738a774c6d1d879ea3e14c307f74ae926eddfdb74105d8f2ab9d3f4
Tx public key: 00beb70cdc7603c41c8dd48fd5eb3d8d2e621ffd5993d5abe91aba26d3d53008
Timestamp: 1725570569 Timestamp [UCT]: 2024-09-05 21:09:29 Age [y:d:h:m:s]: 00:139:06:13:29
Block: 1103742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99552 RingCT/type: yes/0
Extra: 0100beb70cdc7603c41c8dd48fd5eb3d8d2e621ffd5993d5abe91aba26d3d5300802110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f078fcdd611dba0874f7094c53808e73b71603fbbed8cd38800b0a0d38f1863 0.600000000000 1580687 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": 1103752, "vin": [ { "gen": { "height": 1103742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f078fcdd611dba0874f7094c53808e73b71603fbbed8cd38800b0a0d38f1863" } } ], "extra": [ 1, 0, 190, 183, 12, 220, 118, 3, 196, 28, 141, 212, 143, 213, 235, 61, 141, 46, 98, 31, 253, 89, 147, 213, 171, 233, 26, 186, 38, 211, 213, 48, 8, 2, 17, 0, 0, 0, 10, 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