Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7b655aae7e57929b77d80d12b037bf14bfe25b796737e431d710244da329490

Tx prefix hash: 030d96fc410f254d0a3db6971520cb0d52c04c7117a69de611a4ced916cf202b
Tx public key: cf2c295f8e9b7ccb69ff828b756e4c7a03a8880c4dead433422689da43441c55
Timestamp: 1709052122 Timestamp [UCT]: 2024-02-27 16:42:02 Age [y:d:h:m:s]: 01:092:12:10:55
Block: 966801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327163 RingCT/type: yes/0
Extra: 01cf2c295f8e9b7ccb69ff828b756e4c7a03a8880c4dead433422689da43441c550211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8667bad2cb18936e9cb50b2260efc811c853eee3afc31539b4e94ffd9567a6a4 0.600000000000 1426572 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": 966811, "vin": [ { "gen": { "height": 966801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8667bad2cb18936e9cb50b2260efc811c853eee3afc31539b4e94ffd9567a6a4" } } ], "extra": [ 1, 207, 44, 41, 95, 142, 155, 124, 203, 105, 255, 130, 139, 117, 110, 76, 122, 3, 168, 136, 12, 77, 234, 212, 51, 66, 38, 137, 218, 67, 68, 28, 85, 2, 17, 0, 0, 0, 16, 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