Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b12319e6ef893ea21a3edbcb42ae7cc5eaa58946aea50ddd6d10e08d00ec7a97

Tx prefix hash: cca03327f6ba6c1efcb066361f67ccab878b345bedff57cb9b61e392594a5b52
Tx public key: 84d8e324cfaddea71887d719a2c507fdafb3f84bdd38f3036c13954cfbd0f478
Timestamp: 1685360840 Timestamp [UCT]: 2023-05-29 11:47:20 Age [y:d:h:m:s]: 01:235:12:08:56
Block: 770635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429696 RingCT/type: yes/0
Extra: 0184d8e324cfaddea71887d719a2c507fdafb3f84bdd38f3036c13954cfbd0f478021100000002b3164c24000000000000000000

1 output(s) for total of 1.716194525000 dcy

stealth address amount amount idx
00: e84533c612880792ef27d913f77afeb5c682b3bc6dfbbfb909ab1764bd631a41 1.716194525000 1219962 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": 770645, "vin": [ { "gen": { "height": 770635 } } ], "vout": [ { "amount": 1716194525, "target": { "key": "e84533c612880792ef27d913f77afeb5c682b3bc6dfbbfb909ab1764bd631a41" } } ], "extra": [ 1, 132, 216, 227, 36, 207, 173, 222, 167, 24, 135, 215, 25, 162, 197, 7, 253, 175, 179, 248, 75, 221, 56, 243, 3, 108, 19, 149, 76, 251, 208, 244, 120, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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