Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4abe7c973bcc72764220caae572b9c33510f8e84df26a36c830219bdf49d2a06

Tx prefix hash: aea967fff92815820c17dd6e28d0a3d0a88a2700f383d9fe46e77570ad6aab2f
Tx public key: 029c7181d5426cb27c8d0bf6dc3a3d644b80f0fd4a440c20b3fd60ee2ec7e8e5
Timestamp: 1763199744 Timestamp [UCT]: 2025-11-15 09:42:24 Age [y:d:h:m:s]: 00:054:22:12:30
Block: 1412575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39333 RingCT/type: yes/0
Extra: 01029c7181d5426cb27c8d0bf6dc3a3d644b80f0fd4a440c20b3fd60ee2ec7e8e50211000000044e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2185b45a7d6f5ea05951cb2e042d621beca0ee5e3d8929aaf5103a8d2147de69 0.600000000000 1901046 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": 1412585, "vin": [ { "gen": { "height": 1412575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2185b45a7d6f5ea05951cb2e042d621beca0ee5e3d8929aaf5103a8d2147de69" } } ], "extra": [ 1, 2, 156, 113, 129, 213, 66, 108, 178, 124, 141, 11, 246, 220, 58, 61, 100, 75, 128, 240, 253, 74, 68, 12, 32, 179, 253, 96, 238, 46, 199, 232, 229, 2, 17, 0, 0, 0, 4, 78, 123, 252, 9, 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