Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 729f3bb0873b88140833221ca6b83e48d88fb1f8c62b825803cef598ea8b781a

Tx prefix hash: 269822572cde991a4a0949aeabaac48535a7151dc5b7864bcd11c0060e616d5e
Tx public key: 65be3f3f74fbccb9d68dce31cf6ab7ec1b44a50baa944a5bdfe702d58f0a113b
Timestamp: 1716315729 Timestamp [UCT]: 2024-05-21 18:22:09 Age [y:d:h:m:s]: 00:163:03:19:52
Block: 1027010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116777 RingCT/type: yes/0
Extra: 0165be3f3f74fbccb9d68dce31cf6ab7ec1b44a50baa944a5bdfe702d58f0a113b02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dcb959e17679ff2c06bb91f76cd834b3626f349cf4240a2793bf1ec29c5802c 0.600000000000 1494409 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": 1027020, "vin": [ { "gen": { "height": 1027010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dcb959e17679ff2c06bb91f76cd834b3626f349cf4240a2793bf1ec29c5802c" } } ], "extra": [ 1, 101, 190, 63, 63, 116, 251, 204, 185, 214, 141, 206, 49, 207, 106, 183, 236, 27, 68, 165, 11, 170, 148, 74, 91, 223, 231, 2, 213, 143, 10, 17, 59, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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