Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3378bcc734e03bd353476192a690e790091b7f53582a05620f7267b024a4887

Tx prefix hash: 8e897956c1a33105f67cf846b2bd74f0601a4a8891e72f5f960b91c4954298e5
Tx public key: 577e7e9699a89590d3f4c1e3ed536fdc7c936bca741277ee7e609fa3a5a8d9fc
Timestamp: 1609099357 Timestamp [UCT]: 2020-12-27 20:02:37 Age [y:d:h:m:s]: 03:337:08:19:30
Block: 170502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 993523 RingCT/type: yes/0
Extra: 01577e7e9699a89590d3f4c1e3ed536fdc7c936bca741277ee7e609fa3a5a8d9fc021100000022f6643c68000000000000000000

1 output(s) for total of 167.130903249000 dcy

stealth address amount amount idx
00: efb4ed7d16d10e372a95094cc4bb69e317dbd72086d056da5fb9f0da8a82adaa 167.130903249000 319851 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": 170512, "vin": [ { "gen": { "height": 170502 } } ], "vout": [ { "amount": 167130903249, "target": { "key": "efb4ed7d16d10e372a95094cc4bb69e317dbd72086d056da5fb9f0da8a82adaa" } } ], "extra": [ 1, 87, 126, 126, 150, 153, 168, 149, 144, 211, 244, 193, 227, 237, 83, 111, 220, 124, 147, 107, 202, 116, 18, 119, 238, 126, 96, 159, 163, 165, 168, 217, 252, 2, 17, 0, 0, 0, 34, 246, 100, 60, 104, 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