Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b8df9bf4b9b12ee3b3199deed7e58443435efc65d9059b16e806078fb5d95d

Tx prefix hash: 3f27c531f87e0f19de36b955d99e2e66fc57316f43d99104e3f2d9bb8182a4cd
Tx public key: 00739f21f94a142eaf7e8609f87b3e858d142b5bcb679d8bc6e9af8d1ae27014
Timestamp: 1694868028 Timestamp [UCT]: 2023-09-16 12:40:28 Age [y:d:h:m:s]: 02:057:03:40:21
Block: 849389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560521 RingCT/type: yes/0
Extra: 0100739f21f94a142eaf7e8609f87b3e858d142b5bcb679d8bc6e9af8d1ae27014021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.941069509000 dcy

stealth address amount amount idx
00: 36d0aa49a1d26eb5a3a556e19b79a8bd3363a212cfded74ce14a519f0d4fdc4e 0.941069509000 1303053 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": 849399, "vin": [ { "gen": { "height": 849389 } } ], "vout": [ { "amount": 941069509, "target": { "key": "36d0aa49a1d26eb5a3a556e19b79a8bd3363a212cfded74ce14a519f0d4fdc4e" } } ], "extra": [ 1, 0, 115, 159, 33, 249, 74, 20, 46, 175, 126, 134, 9, 248, 123, 62, 133, 141, 20, 43, 91, 203, 103, 157, 139, 198, 233, 175, 141, 26, 226, 112, 20, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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