Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e02a44785677d294e5656acd40008b2e3795957fd5ffe7afbed2ecdd6acf94c2

Tx prefix hash: 19e89ef3824c9a36d6782a2bb9fdbb003dbff022525e8a6a6a560fe778b3aaa5
Tx public key: 2e80e91bfc0f693dd7b4f9ce4919b96ebf944120f2ab1ac299f1433a94a754e2
Timestamp: 1715566084 Timestamp [UCT]: 2024-05-13 02:08:04 Age [y:d:h:m:s]: 01:011:16:56:03
Block: 1020820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269264 RingCT/type: yes/0
Extra: 012e80e91bfc0f693dd7b4f9ce4919b96ebf944120f2ab1ac299f1433a94a754e202110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2661e488b11e690bf03bc3389e6ff428b50b0f35df4fdc5e393a6c4811b5fe61 0.600000000000 1484925 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": 1020830, "vin": [ { "gen": { "height": 1020820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2661e488b11e690bf03bc3389e6ff428b50b0f35df4fdc5e393a6c4811b5fe61" } } ], "extra": [ 1, 46, 128, 233, 27, 252, 15, 105, 61, 215, 180, 249, 206, 73, 25, 185, 110, 191, 148, 65, 32, 242, 171, 26, 194, 153, 241, 67, 58, 148, 167, 84, 226, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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