Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dd74c138a86c76d525efedfc115e094d5d384fc33451ab122a8abb7e85cd9db

Tx prefix hash: d9f8a4accfc0dfc23ada32d0e4645562db1303b5a94b9e2d39abe116e5ab0baf
Tx public key: 4c10ca2712712c6837cb61c843fb64f87f470c0f4d22ca1ea5234bc249e696c5
Timestamp: 1732118655 Timestamp [UCT]: 2024-11-20 16:04:15 Age [y:d:h:m:s]: 00:003:09:36:34
Block: 1157927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2443 RingCT/type: yes/0
Extra: 014c10ca2712712c6837cb61c843fb64f87f470c0f4d22ca1ea5234bc249e696c50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aec7f114aaa4b74e75cb015206a27747f631f934763a2cbe5eecda64d849546 0.600000000000 1643550 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": 1157937, "vin": [ { "gen": { "height": 1157927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aec7f114aaa4b74e75cb015206a27747f631f934763a2cbe5eecda64d849546" } } ], "extra": [ 1, 76, 16, 202, 39, 18, 113, 44, 104, 55, 203, 97, 200, 67, 251, 100, 248, 127, 71, 12, 15, 77, 34, 202, 30, 165, 35, 75, 194, 73, 230, 150, 197, 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