Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1937ea892b8483f6430a0890b5ab155e2636fd12e45854a947bef2f13bb66b26

Tx prefix hash: 5b3eb492e662e2077019833c245f08f645401e19989c2292961b42662b7d34ea
Tx public key: f2136ecb286aa07d5363e69ffcb771f7a061a973553a6fb59abc0a8df1047e18
Timestamp: 1727182291 Timestamp [UCT]: 2024-09-24 12:51:31 Age [y:d:h:m:s]: 01:045:23:45:22
Block: 1117096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291273 RingCT/type: yes/0
Extra: 01f2136ecb286aa07d5363e69ffcb771f7a061a973553a6fb59abc0a8df1047e1802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 900ba9cb0ca05c041594e190eea1e173624afc9b9f5710ce2b3bc5ff0820696a 0.600000000000 1597813 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": 1117106, "vin": [ { "gen": { "height": 1117096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "900ba9cb0ca05c041594e190eea1e173624afc9b9f5710ce2b3bc5ff0820696a" } } ], "extra": [ 1, 242, 19, 110, 203, 40, 106, 160, 125, 83, 99, 230, 159, 252, 183, 113, 247, 160, 97, 169, 115, 85, 58, 111, 181, 154, 188, 10, 141, 241, 4, 126, 24, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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