Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f978c0f53799500273fe1bd773e0c6ac7435d96c7c8705d2fee19f26df6e0174

Tx prefix hash: 29aa1538ad8495a6654ae4e1fb11a2bd541f4b93c1e056b1a93a76a91fc83157
Tx public key: f6faaa7fc238a5ce7a12d088bf36692c7303495ec04bd9378dc5da9c777ceffe
Timestamp: 1703091347 Timestamp [UCT]: 2023-12-20 16:55:47 Age [y:d:h:m:s]: 01:329:20:45:04
Block: 917391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494587 RingCT/type: yes/0
Extra: 01f6faaa7fc238a5ce7a12d088bf36692c7303495ec04bd9378dc5da9c777ceffe02110000000ee08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae205644f28f367f445caa5e6260be37f7750e3fe2fe0f7b6183a6979c056d17 0.600000000000 1374965 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": 917401, "vin": [ { "gen": { "height": 917391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae205644f28f367f445caa5e6260be37f7750e3fe2fe0f7b6183a6979c056d17" } } ], "extra": [ 1, 246, 250, 170, 127, 194, 56, 165, 206, 122, 18, 208, 136, 191, 54, 105, 44, 115, 3, 73, 94, 192, 75, 217, 55, 141, 197, 218, 156, 119, 124, 239, 254, 2, 17, 0, 0, 0, 14, 224, 133, 50, 182, 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