Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d07230498b114550c5414bef675fe9f0e7997f3402a74f4d7728db4a401c5d5

Tx prefix hash: ae88b64ffcf05059991b0fb1ed842924bc549f18bbaee2e25584c7787d80a76c
Tx public key: b9a0ac2716a072dc124a794a51b99b5dcfd2233f81d41f0ab32011e3f52356b4
Timestamp: 1693997198 Timestamp [UCT]: 2023-09-06 10:46:38 Age [y:d:h:m:s]: 01:171:17:32:06
Block: 842160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383805 RingCT/type: yes/0
Extra: 01b9a0ac2716a072dc124a794a51b99b5dcfd2233f81d41f0ab32011e3f52356b40211000000134b8f5122000000000000000000

1 output(s) for total of 0.994430397000 dcy

stealth address amount amount idx
00: 49e2d250161be79e3da455501f4283492f008dca2d4ce647d16a7c016cc5b680 0.994430397000 1295254 of 0

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": 842170, "vin": [ { "gen": { "height": 842160 } } ], "vout": [ { "amount": 994430397, "target": { "key": "49e2d250161be79e3da455501f4283492f008dca2d4ce647d16a7c016cc5b680" } } ], "extra": [ 1, 185, 160, 172, 39, 22, 160, 114, 220, 18, 74, 121, 74, 81, 185, 155, 93, 207, 210, 35, 63, 129, 212, 31, 10, 179, 32, 17, 227, 245, 35, 86, 180, 2, 17, 0, 0, 0, 19, 75, 143, 81, 34, 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