Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a839e84baaed7d0436c6876f29f4a106002560d0078504ca7fd2026a230620a

Tx prefix hash: c0a4095e9cb78cd72bf947f811526acc6d679f5c82d7607838df94629a1746f9
Tx public key: 45942e13c130a4b293de3ce7725bc1c92a28c77ad4ebac3a9ebeff84155075a0
Timestamp: 1696552036 Timestamp [UCT]: 2023-10-06 00:27:16 Age [y:d:h:m:s]: 01:181:01:15:43
Block: 863357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390437 RingCT/type: yes/0
Extra: 0145942e13c130a4b293de3ce7725bc1c92a28c77ad4ebac3a9ebeff84155075a002110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.845940660000 dcy

stealth address amount amount idx
00: 41f776b710c8bdf9a0a0fc426fe7cbd77ca7e96f5e67004c5ce7f8fe70817d41 0.845940660000 1317809 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": 863367, "vin": [ { "gen": { "height": 863357 } } ], "vout": [ { "amount": 845940660, "target": { "key": "41f776b710c8bdf9a0a0fc426fe7cbd77ca7e96f5e67004c5ce7f8fe70817d41" } } ], "extra": [ 1, 69, 148, 46, 19, 193, 48, 164, 178, 147, 222, 60, 231, 114, 91, 193, 201, 42, 40, 199, 122, 212, 235, 172, 58, 158, 190, 255, 132, 21, 80, 117, 160, 2, 17, 0, 0, 0, 11, 250, 243, 92, 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