Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437b817e5e80721196b313481f8491500318a717c3e06b780486b70ec675b590

Tx prefix hash: f1b7dafd84bc7bcabfbc7e245bcc4ec10309528ddfe3dbab7587abf7df54f800
Tx public key: 405e1cfd7bf69630c1813d69e27d3f92a7c97b14b90a73fe91a2c4739fb081b5
Timestamp: 1673976160 Timestamp [UCT]: 2023-01-17 17:22:40 Age [y:d:h:m:s]: 02:309:23:09:27
Block: 676859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 740925 RingCT/type: yes/0
Extra: 01405e1cfd7bf69630c1813d69e27d3f92a7c97b14b90a73fe91a2c4739fb081b50211000000018b7b6602000000000000000000

1 output(s) for total of 3.509822087000 dcy

stealth address amount amount idx
00: 74ff7e06fedea744a55c38d73db1c01f844010e88bc54c1474af40b32bb363fe 3.509822087000 1118614 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": 676869, "vin": [ { "gen": { "height": 676859 } } ], "vout": [ { "amount": 3509822087, "target": { "key": "74ff7e06fedea744a55c38d73db1c01f844010e88bc54c1474af40b32bb363fe" } } ], "extra": [ 1, 64, 94, 28, 253, 123, 246, 150, 48, 193, 129, 61, 105, 226, 125, 63, 146, 167, 201, 123, 20, 185, 10, 115, 254, 145, 162, 196, 115, 159, 176, 129, 181, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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