Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b82d791eddd8c71201a45db39da5f0c0836f398ed2093ec6e739a67ab8f8779

Tx prefix hash: 0dce58a91da5b57f87fb009dd4d7c22cef2beac040212f77e50316fa487292b1
Tx public key: 08386f068537c5cb52adbd6f33f261350f38d76e49a8af6ca39ff2d71a0df112
Timestamp: 1736496759 Timestamp [UCT]: 2025-01-10 08:12:39 Age [y:d:h:m:s]: 00:158:09:44:26
Block: 1194174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112935 RingCT/type: yes/0
Extra: 0108386f068537c5cb52adbd6f33f261350f38d76e49a8af6ca39ff2d71a0df1120211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a7224a5b0e056129d780c3541ca4c525572a9c5b1491042fb6ec5d1db455be4 0.600000000000 1680741 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": 1194184, "vin": [ { "gen": { "height": 1194174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a7224a5b0e056129d780c3541ca4c525572a9c5b1491042fb6ec5d1db455be4" } } ], "extra": [ 1, 8, 56, 111, 6, 133, 55, 197, 203, 82, 173, 189, 111, 51, 242, 97, 53, 15, 56, 215, 110, 73, 168, 175, 108, 163, 159, 242, 215, 26, 13, 241, 18, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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