Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b331748798714ecf791c594c992f1a3169a6352a010ae06b71b7d6376e964bab

Tx prefix hash: 92a6cf4a9f30a3b23766374ff8e379d6e7308dce38c32f6057ca94e9eddb8c06
Tx public key: bf67f5eaf40a0bf1b97a607ad1fe7a89098bcdd02e4a0f502f3130ab23fcc35d
Timestamp: 1712351571 Timestamp [UCT]: 2024-04-05 21:12:51 Age [y:d:h:m:s]: 01:277:06:45:56
Block: 994117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456952 RingCT/type: yes/0
Extra: 01bf67f5eaf40a0bf1b97a607ad1fe7a89098bcdd02e4a0f502f3130ab23fcc35d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26dcf05d7d640ec97cc64b5b2cec24ef044643110d5a4f63bb3f864405231957 0.600000000000 1454517 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": 994127, "vin": [ { "gen": { "height": 994117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26dcf05d7d640ec97cc64b5b2cec24ef044643110d5a4f63bb3f864405231957" } } ], "extra": [ 1, 191, 103, 245, 234, 244, 10, 11, 241, 185, 122, 96, 122, 209, 254, 122, 137, 9, 139, 205, 208, 46, 74, 15, 80, 47, 49, 48, 171, 35, 252, 195, 93, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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