Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638f4e55d211b49e85e7f092347aaa5c068caee7652e7756e4c57eecb5966dba

Tx prefix hash: 9c49edc64b846bd1e452ba7272424c53d144deb464a9871518c4b6bc67b3cb6a
Tx public key: b511205604426eeb022a1b1dcd318403d10931dc485c6b17466fb3f2d2e6f68a
Timestamp: 1681463511 Timestamp [UCT]: 2023-04-14 09:11:51 Age [y:d:h:m:s]: 02:022:15:03:50
Block: 738301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538342 RingCT/type: yes/0
Extra: 01b511205604426eeb022a1b1dcd318403d10931dc485c6b17466fb3f2d2e6f68a021100000001faf35c9c000000000000000000

1 output(s) for total of 2.196354934000 dcy

stealth address amount amount idx
00: 50fa3168674ee302985c07c2876fca1ffff28cfedb533528f7aadda3a116039f 2.196354934000 1184976 of 0

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": 738311, "vin": [ { "gen": { "height": 738301 } } ], "vout": [ { "amount": 2196354934, "target": { "key": "50fa3168674ee302985c07c2876fca1ffff28cfedb533528f7aadda3a116039f" } } ], "extra": [ 1, 181, 17, 32, 86, 4, 66, 110, 235, 2, 42, 27, 29, 205, 49, 132, 3, 209, 9, 49, 220, 72, 92, 107, 23, 70, 111, 179, 242, 210, 230, 246, 138, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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