Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb61e41c4ff61aeb2f6568906878e1c0f53d1b8e3ceca7e52c231b1ef2a7a2bb

Tx prefix hash: fc2436b205f75a48ea47c3ee85220e01d17406e3d0c702e33007f8d0a7fe7331
Tx public key: d9b9529d8583ad7937e847d0365ee939843bce77ba589c8840f520d231f4ba62
Timestamp: 1708077278 Timestamp [UCT]: 2024-02-16 09:54:38 Age [y:d:h:m:s]: 01:058:08:40:07
Block: 958700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302758 RingCT/type: yes/0
Extra: 01d9b9529d8583ad7937e847d0365ee939843bce77ba589c8840f520d231f4ba6202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0dc960741d370dcb867cb5083d0e16d695d4c0b0aaf4248d8426fadf265711a 0.600000000000 1418061 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": 958710, "vin": [ { "gen": { "height": 958700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0dc960741d370dcb867cb5083d0e16d695d4c0b0aaf4248d8426fadf265711a" } } ], "extra": [ 1, 217, 185, 82, 157, 133, 131, 173, 121, 55, 232, 71, 208, 54, 94, 233, 57, 132, 59, 206, 119, 186, 88, 156, 136, 64, 245, 32, 210, 49, 244, 186, 98, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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