Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 853252d3535a54af53d5bbc0422a1e04d27b77ac7cd9cc8a8008786463fdbcd8

Tx prefix hash: 4708b6b7d0f3a8f18f6315cedfeb0a4fa47658c8d34406e68df023a0cd736e09
Tx public key: 4b0e214ffe8256fa793301d7eef9b28ec5ea29c7a709692b20cb0af4b383b03e
Timestamp: 1684843759 Timestamp [UCT]: 2023-05-23 12:09:19 Age [y:d:h:m:s]: 01:277:07:38:32
Block: 766355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459360 RingCT/type: yes/0
Extra: 014b0e214ffe8256fa793301d7eef9b28ec5ea29c7a709692b20cb0af4b383b03e02110000000475e3f0e9000000000000000000

1 output(s) for total of 1.773160038000 dcy

stealth address amount amount idx
00: 2dec3e66b9ba9c2b42ab5428aea79219e1b12c9a8fce4313dcb4f0c60e30e9d5 1.773160038000 1215390 of 0

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": 766365, "vin": [ { "gen": { "height": 766355 } } ], "vout": [ { "amount": 1773160038, "target": { "key": "2dec3e66b9ba9c2b42ab5428aea79219e1b12c9a8fce4313dcb4f0c60e30e9d5" } } ], "extra": [ 1, 75, 14, 33, 79, 254, 130, 86, 250, 121, 51, 1, 215, 238, 249, 178, 142, 197, 234, 41, 199, 167, 9, 105, 43, 32, 203, 10, 244, 179, 131, 176, 62, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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