Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9623bf1a112299b03b5c0396df721fd9881c6c15ce9c0809fb4807c21a6a848

Tx prefix hash: 10acb3cc8473ee469af3aa1751668cd7d1376149f93312e6fa70e1096509baf9
Tx public key: 939c13f2e6c61b177060e2e85a609172e8b06f4b941ff41a1d2ab1b4834ef12c
Timestamp: 1736416033 Timestamp [UCT]: 2025-01-09 09:47:13 Age [y:d:h:m:s]: 00:070:04:55:32
Block: 1193506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49986 RingCT/type: yes/0
Extra: 01939c13f2e6c61b177060e2e85a609172e8b06f4b941ff41a1d2ab1b4834ef12c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c634c445e407b56bcebede62daa79e504c1d4ed72579d7b2ab39d6fcaedc4ca1 0.600000000000 1680067 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": 1193516, "vin": [ { "gen": { "height": 1193506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c634c445e407b56bcebede62daa79e504c1d4ed72579d7b2ab39d6fcaedc4ca1" } } ], "extra": [ 1, 147, 156, 19, 242, 230, 198, 27, 23, 112, 96, 226, 232, 90, 96, 145, 114, 232, 176, 111, 75, 148, 31, 244, 26, 29, 42, 177, 180, 131, 78, 241, 44, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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