Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63a74e04106997bfeb8c24841d03737c93dd5c92c7e1c9c4a3739dff0196bf1c

Tx prefix hash: 09332b3c66275ec70b56e52a09ccb69f8b20bf2b0e16c5cbb238c4a0506589e1
Tx public key: a2b2324b6e0d324796f2276e218b1bc83888df0098c7d954ebe531f4193cca80
Timestamp: 1719446082 Timestamp [UCT]: 2024-06-26 23:54:42 Age [y:d:h:m:s]: 00:263:11:22:17
Block: 1052953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188285 RingCT/type: yes/0
Extra: 01a2b2324b6e0d324796f2276e218b1bc83888df0098c7d954ebe531f4193cca8002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b21a6fffba49c52dfa94137e603a47bf8efc3a27c46817ca5f569f2148b11c2 0.600000000000 1523298 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": 1052963, "vin": [ { "gen": { "height": 1052953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b21a6fffba49c52dfa94137e603a47bf8efc3a27c46817ca5f569f2148b11c2" } } ], "extra": [ 1, 162, 178, 50, 75, 110, 13, 50, 71, 150, 242, 39, 110, 33, 139, 27, 200, 56, 136, 223, 0, 152, 199, 217, 84, 235, 229, 49, 244, 25, 60, 202, 128, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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