Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c173761f6ec01ba6b74beb07978af88d57bbe2d24d482bd8aebe2603efd6d75b

Tx prefix hash: 7f42dda2326f8701c6ced3b0510ccc3bba2a5c346023c8f1a3a6a0b73d8e43df
Tx public key: 2e88e448a98bfa0a6e522762d67d2475ad4930a8d4a9e98613564e08a16fdd48
Timestamp: 1704919686 Timestamp [UCT]: 2024-01-10 20:48:06 Age [y:d:h:m:s]: 01:075:14:12:21
Block: 932517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315104 RingCT/type: yes/0
Extra: 012e88e448a98bfa0a6e522762d67d2475ad4930a8d4a9e98613564e08a16fdd480211000000029da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af4766cd46935f784069af4a101762cc969d9a942d98b7b05ff21d691d6ca026 0.600000000000 1390453 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": 932527, "vin": [ { "gen": { "height": 932517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af4766cd46935f784069af4a101762cc969d9a942d98b7b05ff21d691d6ca026" } } ], "extra": [ 1, 46, 136, 228, 72, 169, 139, 250, 10, 110, 82, 39, 98, 214, 125, 36, 117, 173, 73, 48, 168, 212, 169, 233, 134, 19, 86, 78, 8, 161, 111, 221, 72, 2, 17, 0, 0, 0, 2, 157, 168, 225, 52, 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