Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2ee5edda0f88888b0ff8d1e07647e62ad28fcb8db1f3921755dc34f51ee334d

Tx prefix hash: dd428607044deb0c04a5f68ec5a8be23b219e3433ca16317b1499c52027d73c4
Tx public key: e7a72a1dd7c1f77168bf6ed2d2740c420b5858d384d472252a3b4f7dec840e9a
Timestamp: 1717201571 Timestamp [UCT]: 2024-06-01 00:26:11 Age [y:d:h:m:s]: 00:313:22:08:13
Block: 1034363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224355 RingCT/type: yes/0
Extra: 01e7a72a1dd7c1f77168bf6ed2d2740c420b5858d384d472252a3b4f7dec840e9a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 649629f7e5dd15d8d632aa2920a282891310f8d2d07970969390e430d53b60b5 0.600000000000 1502868 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": 1034373, "vin": [ { "gen": { "height": 1034363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "649629f7e5dd15d8d632aa2920a282891310f8d2d07970969390e430d53b60b5" } } ], "extra": [ 1, 231, 167, 42, 29, 215, 193, 247, 113, 104, 191, 110, 210, 210, 116, 12, 66, 11, 88, 88, 211, 132, 212, 114, 37, 42, 59, 79, 125, 236, 132, 14, 154, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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