Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dca765f9ada5510d7b71e6858a956d469a11e13aebb57aa936c71c1d45bde92d

Tx prefix hash: 70888d08c0623381fd91b0f19c3913b433b631211fea870ab6a14ef287172b9f
Tx public key: 02a7b21a0ab8a09f9dc4fc5679ce1c5430ec40ea14d88fbf72f01347ab14a98a
Timestamp: 1724354146 Timestamp [UCT]: 2024-08-22 19:15:46 Age [y:d:h:m:s]: 00:093:22:43:38
Block: 1093666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67183 RingCT/type: yes/0
Extra: 0102a7b21a0ab8a09f9dc4fc5679ce1c5430ec40ea14d88fbf72f01347ab14a98a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e94f309ea715b0f60efeffb993ec59fb615061ec3cda2802975cff024eeab5c0 0.600000000000 1568655 of 15

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": 1093676, "vin": [ { "gen": { "height": 1093666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e94f309ea715b0f60efeffb993ec59fb615061ec3cda2802975cff024eeab5c0" } } ], "extra": [ 1, 2, 167, 178, 26, 10, 184, 160, 159, 157, 196, 252, 86, 121, 206, 28, 84, 48, 236, 64, 234, 20, 216, 143, 191, 114, 240, 19, 71, 171, 20, 169, 138, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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