Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be48c101cb4eb175e6f785ed6b28fbfb3e035703d92b37516a61dc7136c51b85

Tx prefix hash: eb9d9f1f00902f9539824186aeb714a293f8bd33125d8d602c8fe0fdd2cfc20c
Tx public key: 4e0fb68fcdc596a1e8bb8c6c17bed460dc7b95f0e8c2081feeb12f9571f94923
Timestamp: 1717946038 Timestamp [UCT]: 2024-06-09 15:13:58 Age [y:d:h:m:s]: 00:295:23:06:19
Block: 1040530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211495 RingCT/type: yes/0
Extra: 014e0fb68fcdc596a1e8bb8c6c17bed460dc7b95f0e8c2081feeb12f9571f9492302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ae51c04d0e73fe1a6b0ea2c11d3bac7ca3ae55ab6073f4b08b58a0c67cfdc75 0.600000000000 1509187 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": 1040540, "vin": [ { "gen": { "height": 1040530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ae51c04d0e73fe1a6b0ea2c11d3bac7ca3ae55ab6073f4b08b58a0c67cfdc75" } } ], "extra": [ 1, 78, 15, 182, 143, 205, 197, 150, 161, 232, 187, 140, 108, 23, 190, 212, 96, 220, 123, 149, 240, 232, 194, 8, 31, 238, 177, 47, 149, 113, 249, 73, 35, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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