Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 532d192c4568cf02c294642abc4ef1555bec329b41c6c592a7f9cc76546c519d

Tx prefix hash: d2a68c8220fa0108b6c29c44dee94a20b9858b057402db25f139c2370d050ad2
Tx public key: 9d21dcb93af6006450e614161816b536e5cb6ce6960a7195b89df175ba367652
Timestamp: 1697318658 Timestamp [UCT]: 2023-10-14 21:24:18 Age [y:d:h:m:s]: 01:193:17:06:14
Block: 869725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399486 RingCT/type: yes/0
Extra: 019d21dcb93af6006450e614161816b536e5cb6ce6960a7195b89df175ba36765202110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.805823749000 dcy

stealth address amount amount idx
00: b894c77ec1b502c9bb566d6d8f3a8460f87935fec3b386752c6d4a2bb1b04b69 0.805823749000 1324580 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": 869735, "vin": [ { "gen": { "height": 869725 } } ], "vout": [ { "amount": 805823749, "target": { "key": "b894c77ec1b502c9bb566d6d8f3a8460f87935fec3b386752c6d4a2bb1b04b69" } } ], "extra": [ 1, 157, 33, 220, 185, 58, 246, 0, 100, 80, 230, 20, 22, 24, 22, 181, 54, 229, 203, 108, 230, 150, 10, 113, 149, 184, 157, 241, 117, 186, 54, 118, 82, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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