Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f992b8a17a55e3857da31131b3acd0b18d519287c02db9ab1e94b943eb78d624

Tx prefix hash: e2c2cccfc118644d5968e0d80f17f449d8555d6b12391bbfd6374f977d811899
Tx public key: 8d4f4866119d52ecaddd77b31533b139170fbfa35e6f568430c4169e3f987a44
Timestamp: 1632424669 Timestamp [UCT]: 2021-09-23 19:17:49 Age [y:d:h:m:s]: 03:093:23:47:56
Block: 339594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 843477 RingCT/type: yes/0
Extra: 018d4f4866119d52ecaddd77b31533b139170fbfa35e6f568430c4169e3f987a440211000000113fc41461000000000000000000

1 output(s) for total of 46.003628851000 dcy

stealth address amount amount idx
00: 7ae49889f1f5a475c3999fba871ba8d8c6491b1e966d56db8d21d899094f441d 46.003628851000 698373 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": 339604, "vin": [ { "gen": { "height": 339594 } } ], "vout": [ { "amount": 46003628851, "target": { "key": "7ae49889f1f5a475c3999fba871ba8d8c6491b1e966d56db8d21d899094f441d" } } ], "extra": [ 1, 141, 79, 72, 102, 17, 157, 82, 236, 173, 221, 119, 179, 21, 51, 177, 57, 23, 15, 191, 163, 94, 111, 86, 132, 48, 196, 22, 158, 63, 152, 122, 68, 2, 17, 0, 0, 0, 17, 63, 196, 20, 97, 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