Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f60e87bb542e66ef631c2b3f6180a2259801a5940f593ed9d7852cd2433ddd6

Tx prefix hash: 9166440ff4ed061b0c389b585e55b58fb6025f014de5a054886f6d62f0fcafb8
Tx public key: 1c2bc3e7ec3ac5adf8d25e70836721b641ff9097c2a12925444521bfc77a4bf8
Timestamp: 1740486186 Timestamp [UCT]: 2025-02-25 12:23:06 Age [y:d:h:m:s]: 00:319:03:20:42
Block: 1226925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225942 RingCT/type: yes/0
Extra: 011c2bc3e7ec3ac5adf8d25e70836721b641ff9097c2a12925444521bfc77a4bf8021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af5c08b28b1e55b32749a67a0b601042afaad83934057930a4cf8e78fa040b40 0.600000000000 1713798 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": 1226935, "vin": [ { "gen": { "height": 1226925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af5c08b28b1e55b32749a67a0b601042afaad83934057930a4cf8e78fa040b40" } } ], "extra": [ 1, 28, 43, 195, 231, 236, 58, 197, 173, 248, 210, 94, 112, 131, 103, 33, 182, 65, 255, 144, 151, 194, 161, 41, 37, 68, 69, 33, 191, 199, 122, 75, 248, 2, 17, 0, 0, 0, 9, 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