Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be331ce664562c6ceb6597c32bd35612b4ecc539085c48e4710a7715c6321f8c

Tx prefix hash: fb981ae4993c711de37a62ed0895817704188d081c54e9d7c9801f683f324bd7
Tx public key: b4a8105271030b8bca8b594089da343805a67cf0724e7c9fb43abfdba1dcde83
Timestamp: 1727949499 Timestamp [UCT]: 2024-10-03 09:58:19 Age [y:d:h:m:s]: 00:162:22:02:29
Block: 1123463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116249 RingCT/type: yes/0
Extra: 01b4a8105271030b8bca8b594089da343805a67cf0724e7c9fb43abfdba1dcde83021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6e3c33c8d79c8279e192c5d5839be718dba788207a4f20802fdc276b41bfb52 0.600000000000 1605998 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": 1123473, "vin": [ { "gen": { "height": 1123463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6e3c33c8d79c8279e192c5d5839be718dba788207a4f20802fdc276b41bfb52" } } ], "extra": [ 1, 180, 168, 16, 82, 113, 3, 11, 139, 202, 139, 89, 64, 137, 218, 52, 56, 5, 166, 124, 240, 114, 78, 124, 159, 180, 58, 191, 219, 161, 220, 222, 131, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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