Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c472da4b55f1ea322bb09f8b884a077d77fb97cd604a316d2334d6bb04218b

Tx prefix hash: 682d5ceadb470a3434bff653388501fa17d81e4eb4c0becc84315cb8bfc6eea7
Tx public key: 4a6a79aeb21bc098ffaa40b482351d81cb4d56686f252298c06c0ceca0012a75
Timestamp: 1723153383 Timestamp [UCT]: 2024-08-08 21:43:03 Age [y:d:h:m:s]: 01:091:05:20:48
Block: 1083694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323675 RingCT/type: yes/0
Extra: 014a6a79aeb21bc098ffaa40b482351d81cb4d56686f252298c06c0ceca0012a75021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7344d50b1f6ca67a0f6a6dbdc5933f941fd9b40daee2fc360b4a6103838ebc9 0.600000000000 1557705 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": 1083704, "vin": [ { "gen": { "height": 1083694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7344d50b1f6ca67a0f6a6dbdc5933f941fd9b40daee2fc360b4a6103838ebc9" } } ], "extra": [ 1, 74, 106, 121, 174, 178, 27, 192, 152, 255, 170, 64, 180, 130, 53, 29, 129, 203, 77, 86, 104, 111, 37, 34, 152, 192, 108, 12, 236, 160, 1, 42, 117, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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