Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcab1cc651044efcac569554cc2732621f00119f391b5b840ee573d0d214c248

Tx prefix hash: 6a0853ffeda2a602fda474980b3a3941928c8deb5c98b32c12afc54765a7d408
Tx public key: 1eddb99b3f90b6e556dceaf1487d29ca8a83d044b3368d5cf80e8734976020c3
Timestamp: 1672692059 Timestamp [UCT]: 2023-01-02 20:40:59 Age [y:d:h:m:s]: 02:103:22:25:55
Block: 666217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595970 RingCT/type: yes/0
Extra: 011eddb99b3f90b6e556dceaf1487d29ca8a83d044b3368d5cf80e8734976020c30211000000025029cbac000000000000000000

1 output(s) for total of 3.806680978000 dcy

stealth address amount amount idx
00: 806ab535a0c0ea7d1e0ae1273bec2c0447c3d638dfe54b0c7c0c331b4c7964b2 3.806680978000 1107320 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": 666227, "vin": [ { "gen": { "height": 666217 } } ], "vout": [ { "amount": 3806680978, "target": { "key": "806ab535a0c0ea7d1e0ae1273bec2c0447c3d638dfe54b0c7c0c331b4c7964b2" } } ], "extra": [ 1, 30, 221, 185, 155, 63, 144, 182, 229, 86, 220, 234, 241, 72, 125, 41, 202, 138, 131, 208, 68, 179, 54, 141, 92, 248, 14, 135, 52, 151, 96, 32, 195, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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