Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa51338ba16d54c9fdaf3c25c495658e055dee51bc061777f4ab78799fc5d31a

Tx prefix hash: 81729fd2eae745eda2e7701b6fcf5d6de1a28adfd18c7afb07802fb4d005121c
Tx public key: 27a9f48b4452ea896285c1eec11d529fb41ab98865550f115a0cc8e586a66503
Timestamp: 1696646585 Timestamp [UCT]: 2023-10-07 02:43:05 Age [y:d:h:m:s]: 01:148:14:49:27
Block: 864141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367242 RingCT/type: yes/0
Extra: 0127a9f48b4452ea896285c1eec11d529fb41ab98865550f115a0cc8e586a6650302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.840895795000 dcy

stealth address amount amount idx
00: 1ce7bc99a0a40281d1e599637fcbc0fd4cbedec30b854575285579415bc6d2ca 0.840895795000 1318649 of 0

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": 864151, "vin": [ { "gen": { "height": 864141 } } ], "vout": [ { "amount": 840895795, "target": { "key": "1ce7bc99a0a40281d1e599637fcbc0fd4cbedec30b854575285579415bc6d2ca" } } ], "extra": [ 1, 39, 169, 244, 139, 68, 82, 234, 137, 98, 133, 193, 238, 193, 29, 82, 159, 180, 26, 185, 136, 101, 85, 15, 17, 90, 12, 200, 229, 134, 166, 101, 3, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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