Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8e3326be2784aeb98e769c29a7211910e13f71feb465da51c6392b2c7248297

Tx prefix hash: 0569c75833ab621c5a7c77290c038df68c4da4d9ae1f4200e838c8f1c337f1d3
Tx public key: d1e81ee7d10911eb455c017afc54115f46bbdd91289c8b45d87cea7cca5064ba
Timestamp: 1694108511 Timestamp [UCT]: 2023-09-07 17:41:51 Age [y:d:h:m:s]: 01:267:02:22:14
Block: 843082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452052 RingCT/type: yes/0
Extra: 01d1e81ee7d10911eb455c017afc54115f46bbdd91289c8b45d87cea7cca5064ba02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.987459792000 dcy

stealth address amount amount idx
00: 155cfbe38e2aa670d0fa3fc4b88a2f8ea15eebe1f2ac54cd35779fbe6159773e 0.987459792000 1296284 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": 843092, "vin": [ { "gen": { "height": 843082 } } ], "vout": [ { "amount": 987459792, "target": { "key": "155cfbe38e2aa670d0fa3fc4b88a2f8ea15eebe1f2ac54cd35779fbe6159773e" } } ], "extra": [ 1, 209, 232, 30, 231, 209, 9, 17, 235, 69, 92, 1, 122, 252, 84, 17, 95, 70, 187, 221, 145, 40, 156, 139, 69, 216, 124, 234, 124, 202, 80, 100, 186, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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