Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 622b92166db17b32302d8d22c51127eb63d411fddc14932b1d6535bcfab5b4a6

Tx prefix hash: 128e68371fd4c1f51bf144313091ddcc1b6a60a2f94bd21ff0bf91d12117cdcb
Tx public key: 5c6ca7e64ff427244eb45700fd0b34b3b54296c7c2b653c4eedc5833d0f28812
Timestamp: 1736074917 Timestamp [UCT]: 2025-01-05 11:01:57 Age [y:d:h:m:s]: 00:164:10:09:29
Block: 1190701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117191 RingCT/type: yes/0
Extra: 015c6ca7e64ff427244eb45700fd0b34b3b54296c7c2b653c4eedc5833d0f2881202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf6f54e0784e90732eeb14fa4ee79691564fcb8b989a759992ead0e9af6d7aa4 0.600000000000 1677218 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": 1190711, "vin": [ { "gen": { "height": 1190701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf6f54e0784e90732eeb14fa4ee79691564fcb8b989a759992ead0e9af6d7aa4" } } ], "extra": [ 1, 92, 108, 167, 230, 79, 244, 39, 36, 78, 180, 87, 0, 253, 11, 52, 179, 181, 66, 150, 199, 194, 182, 83, 196, 238, 220, 88, 51, 208, 242, 136, 18, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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