Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8332a67b3aa9b1cacc4fde96daf8f5851e83cc74d559baac171ab1875cb88c4c

Tx prefix hash: 7b129f4abd498e5406dc5e6c5b8a22c3b11959c342e4e1659e062c2b8a142570
Tx public key: f3d8351ee5c87e44777fd0fcb79daac8d1eaf63e9b73d220db28b345fd7c2ff0
Timestamp: 1732411677 Timestamp [UCT]: 2024-11-24 01:27:57 Age [y:d:h:m:s]: 00:114:14:19:53
Block: 1160358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81723 RingCT/type: yes/0
Extra: 01f3d8351ee5c87e44777fd0fcb79daac8d1eaf63e9b73d220db28b345fd7c2ff0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 986d33e929431b2d7db48fdb8bb9e944c5ce8aa9d7332be5e7cfa497623c92f7 0.600000000000 1646003 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": 1160368, "vin": [ { "gen": { "height": 1160358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "986d33e929431b2d7db48fdb8bb9e944c5ce8aa9d7332be5e7cfa497623c92f7" } } ], "extra": [ 1, 243, 216, 53, 30, 229, 200, 126, 68, 119, 127, 208, 252, 183, 157, 170, 200, 209, 234, 246, 62, 155, 115, 210, 32, 219, 40, 179, 69, 253, 124, 47, 240, 2, 17, 0, 0, 0, 2, 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