Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea3e2a69a773c18b2684334e731d688aa41e236a1f7e7ba57bbf7f6fd30af26

Tx prefix hash: a69c9a36cc184aabd3ac5c49987576ca26b058412affec91a983f363939a780f
Tx public key: b10eea64d5e9a3d3cd6b1cc8fec517e1893ff9329ac2d271001ca59ce42e872d
Timestamp: 1763003925 Timestamp [UCT]: 2025-11-13 03:18:45 Age [y:d:h:m:s]: 00:040:14:27:48
Block: 1410946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29074 RingCT/type: yes/0
Extra: 01b10eea64d5e9a3d3cd6b1cc8fec517e1893ff9329ac2d271001ca59ce42e872d021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b482e04beaf85bb92d37a6068711ae5d0be5ba9b0ec70d817fbeb767783ccdb 0.600000000000 1899401 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": 1410956, "vin": [ { "gen": { "height": 1410946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b482e04beaf85bb92d37a6068711ae5d0be5ba9b0ec70d817fbeb767783ccdb" } } ], "extra": [ 1, 177, 14, 234, 100, 213, 233, 163, 211, 205, 107, 28, 200, 254, 197, 23, 225, 137, 63, 249, 50, 154, 194, 210, 113, 0, 28, 165, 156, 228, 46, 135, 45, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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