Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abea43b173aada4d58d2795c590e0d7c44df874a6e1935278b7b98e5a287e8a3

Tx prefix hash: 1c173036f3c5f98e94e8e5860edd6aa63e2bf32a7ab6e34cb3e0cce7117cfe3d
Tx public key: 415fc907c697c79d46073f02b7170c8fdb9934f58c086ace5134af4d17f865b6
Timestamp: 1583530559 Timestamp [UCT]: 2020-03-06 21:35:59 Age [y:d:h:m:s]: 05:054:02:24:36
Block: 77631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194011 RingCT/type: yes/0
Extra: 01415fc907c697c79d46073f02b7170c8fdb9934f58c086ace5134af4d17f865b60211000000118a2ee0d9000000000000000000

1 output(s) for total of 339.484827991000 dcy

stealth address amount amount idx
00: 5e6ae9819d35d75788f5600e3d7e4e816c51e09e7c46cfff88911dd362d73279 339.484827991000 142778 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": 77641, "vin": [ { "gen": { "height": 77631 } } ], "vout": [ { "amount": 339484827991, "target": { "key": "5e6ae9819d35d75788f5600e3d7e4e816c51e09e7c46cfff88911dd362d73279" } } ], "extra": [ 1, 65, 95, 201, 7, 198, 151, 199, 157, 70, 7, 63, 2, 183, 23, 12, 143, 219, 153, 52, 245, 140, 8, 106, 206, 81, 52, 175, 77, 23, 248, 101, 182, 2, 17, 0, 0, 0, 17, 138, 46, 224, 217, 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