Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e8397f31c2d49039b30d5d6bdc9d30223a965574dea9ca5464074f635ac9ef

Tx prefix hash: 8c8d1aea1099ed39db31fe985b1eaf8cf7c3669ca2f765bb183eb5233aeeabd4
Tx public key: 1eaf6c1e0a9c723b72edfd1365f36ad71b2c1fe36c42c2b39a23b61bdd1e05c8
Timestamp: 1721622665 Timestamp [UCT]: 2024-07-22 04:31:05 Age [y:d:h:m:s]: 00:267:15:18:41
Block: 1070997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191215 RingCT/type: yes/0
Extra: 011eaf6c1e0a9c723b72edfd1365f36ad71b2c1fe36c42c2b39a23b61bdd1e05c802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4feb3eb1b34dacc12feb5da53b93396d9f9f92893913afdda941b0e307fe86b8 0.600000000000 1543060 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": 1071007, "vin": [ { "gen": { "height": 1070997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4feb3eb1b34dacc12feb5da53b93396d9f9f92893913afdda941b0e307fe86b8" } } ], "extra": [ 1, 30, 175, 108, 30, 10, 156, 114, 59, 114, 237, 253, 19, 101, 243, 106, 215, 27, 44, 31, 227, 108, 66, 194, 179, 154, 35, 182, 27, 221, 30, 5, 200, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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