Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cae4048d419537bb8d3bcc236b2f6c514d447117fa1a5b275569da8dae4feef

Tx prefix hash: 4336ea9bfcb5deab8e4e1e2856dfac6da1df74ae1e968fdfa4b20c9da08e6d4c
Tx public key: 5b65a05c09d4a9206f2c8a2cef8c32e53d3604a584577405b0f8d75c3c06e6c8
Timestamp: 1729627359 Timestamp [UCT]: 2024-10-22 20:02:39 Age [y:d:h:m:s]: 00:142:02:34:04
Block: 1137342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101366 RingCT/type: yes/0
Extra: 015b65a05c09d4a9206f2c8a2cef8c32e53d3604a584577405b0f8d75c3c06e6c8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d79394d53cf3db862209e5c53e4763d7ed47e35fb201c38fc53233914383eb12 0.600000000000 1620815 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": 1137352, "vin": [ { "gen": { "height": 1137342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d79394d53cf3db862209e5c53e4763d7ed47e35fb201c38fc53233914383eb12" } } ], "extra": [ 1, 91, 101, 160, 92, 9, 212, 169, 32, 111, 44, 138, 44, 239, 140, 50, 229, 61, 54, 4, 165, 132, 87, 116, 5, 176, 248, 215, 92, 60, 6, 230, 200, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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