Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e9e856702ea58c7bbe2d79530c17f4526bb01c4d26f93f0d3c8d33ec0854ec8

Tx prefix hash: 152ff38da1cddada507e110852dd0d4d13a192d792212e43d88163335e28dae7
Tx public key: 8c42b6022543a2f0331a787cf1b2280d4d2e26cf0cb93ae0bfb6f8c117d757ab
Timestamp: 1731990650 Timestamp [UCT]: 2024-11-19 04:30:50 Age [y:d:h:m:s]: 00:214:18:33:28
Block: 1156870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153185 RingCT/type: yes/0
Extra: 018c42b6022543a2f0331a787cf1b2280d4d2e26cf0cb93ae0bfb6f8c117d757ab0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e47dac8fd8466240aa327091471e3aa7be9dce2974618815b4173a385d73ffc5 0.600000000000 1642493 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": 1156880, "vin": [ { "gen": { "height": 1156870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e47dac8fd8466240aa327091471e3aa7be9dce2974618815b4173a385d73ffc5" } } ], "extra": [ 1, 140, 66, 182, 2, 37, 67, 162, 240, 51, 26, 120, 124, 241, 178, 40, 13, 77, 46, 38, 207, 12, 185, 58, 224, 191, 182, 248, 193, 23, 215, 87, 171, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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