Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83d6245686541b2e7a598e29f214f4891a56b7c043a24d63cac697b85665de57

Tx prefix hash: 489fd457470ebfc85b8072cca75d88ef622811aad77b84c8869cb97425ac3ea5
Tx public key: 464f5c76d44563457c088d517be0b88141df22d97dafb1dfe177b3b59f058e5e
Timestamp: 1707775045 Timestamp [UCT]: 2024-02-12 21:57:25 Age [y:d:h:m:s]: 01:052:14:53:16
Block: 956198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298651 RingCT/type: yes/0
Extra: 01464f5c76d44563457c088d517be0b88141df22d97dafb1dfe177b3b59f058e5e021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 445f04b1f09bedf54daf8ccc7401e6b99a25be5b3c3051fc45207fecec90043b 0.600000000000 1415502 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": 956208, "vin": [ { "gen": { "height": 956198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "445f04b1f09bedf54daf8ccc7401e6b99a25be5b3c3051fc45207fecec90043b" } } ], "extra": [ 1, 70, 79, 92, 118, 212, 69, 99, 69, 124, 8, 141, 81, 123, 224, 184, 129, 65, 223, 34, 217, 125, 175, 177, 223, 225, 119, 179, 181, 159, 5, 142, 94, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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