Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf9db9289c10f2aeb7ae044845b0e6f7c8dcaee19ff6acc577e26094fe40b5ab

Tx prefix hash: 36ffcc157cfd627e7c7e829c32cfeafb1b8069be831ac7a92611e500e5939762
Tx public key: a0757fa58b82c4d9c79e32c532be59d446bd171ebec91973eea820793b728b0d
Timestamp: 1710076996 Timestamp [UCT]: 2024-03-10 13:23:16 Age [y:d:h:m:s]: 01:008:22:08:26
Block: 975304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267370 RingCT/type: yes/0
Extra: 01a0757fa58b82c4d9c79e32c532be59d446bd171ebec91973eea820793b728b0d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd1bb273abd2f0a339f2bbbd8304c617fb0b68fdf7486863cf14dd44ce697556 0.600000000000 1435275 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": 975314, "vin": [ { "gen": { "height": 975304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd1bb273abd2f0a339f2bbbd8304c617fb0b68fdf7486863cf14dd44ce697556" } } ], "extra": [ 1, 160, 117, 127, 165, 139, 130, 196, 217, 199, 158, 50, 197, 50, 190, 89, 212, 70, 189, 23, 30, 190, 201, 25, 115, 238, 168, 32, 121, 59, 114, 139, 13, 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