Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 748b624c4db8dd5824d1675d0199810dfad24c3e0463afc1d781b53fcccf7f3b

Tx prefix hash: fc93c810e018f2d30e38a6cff237cbdb221596347b951d6f16c48ebc7a808bf8
Tx public key: 22cd7a0b8e0e789294c92cc955e4050ef2439e8c9af1a5d7d581a2f8f4960e1c
Timestamp: 1763250908 Timestamp [UCT]: 2025-11-15 23:55:08 Age [y:d:h:m:s]: 00:012:07:10:24
Block: 1413007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8799 RingCT/type: yes/0
Extra: 0122cd7a0b8e0e789294c92cc955e4050ef2439e8c9af1a5d7d581a2f8f4960e1c021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de7e58671e64566326f80e9bd320d0ba7f4d8bd3f9bfd7f392e7d8ee49faf4db 0.600000000000 1901484 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": 1413017, "vin": [ { "gen": { "height": 1413007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de7e58671e64566326f80e9bd320d0ba7f4d8bd3f9bfd7f392e7d8ee49faf4db" } } ], "extra": [ 1, 34, 205, 122, 11, 142, 14, 120, 146, 148, 201, 44, 201, 85, 228, 5, 14, 242, 67, 158, 140, 154, 241, 165, 215, 213, 129, 162, 248, 244, 150, 14, 28, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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