Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46f3c764f0ac4b2b8e26a1e0c44eae0382bb029f9708afe74d499b86fe0a5fd4

Tx prefix hash: 79dc6b414416152d0dc8c274ff80d91713241edc4fd5dc704711a0e8c8ff9cb2
Tx public key: 5b6a1bae41776ba4728c1536f017059e476339ae4afe21548d30210b3a141b7e
Timestamp: 1701256141 Timestamp [UCT]: 2023-11-29 11:09:01 Age [y:d:h:m:s]: 01:086:05:34:13
Block: 902160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322748 RingCT/type: yes/0
Extra: 015b6a1bae41776ba4728c1536f017059e476339ae4afe21548d30210b3a141b7e02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.629172013000 dcy

stealth address amount amount idx
00: 0172d30ef35d200af6352b9a2b628a969b49fe5a7ac53ac98191cd57eedeaea9 0.629172013000 1358775 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": 902170, "vin": [ { "gen": { "height": 902160 } } ], "vout": [ { "amount": 629172013, "target": { "key": "0172d30ef35d200af6352b9a2b628a969b49fe5a7ac53ac98191cd57eedeaea9" } } ], "extra": [ 1, 91, 106, 27, 174, 65, 119, 107, 164, 114, 140, 21, 54, 240, 23, 5, 158, 71, 99, 57, 174, 74, 254, 33, 84, 141, 48, 33, 11, 58, 20, 27, 126, 2, 17, 0, 0, 0, 6, 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