Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eebd3b2befbc5b82ca03589c0ab63dc0d41600fc403b76b77707fd4c56f10955

Tx prefix hash: f70d430e77d2e6bfd2bbf5d19aa743c800c5d55a9d5276ad033c0f3411a98ed5
Tx public key: 1ccba222a409e4eb4c152956e024a9a3cd7c4a498fde4263ff43d7f8a4a625cd
Timestamp: 1751132224 Timestamp [UCT]: 2025-06-28 17:37:04 Age [y:d:h:m:s]: 00:138:20:03:47
Block: 1314667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97311 RingCT/type: yes/0
Extra: 011ccba222a409e4eb4c152956e024a9a3cd7c4a498fde4263ff43d7f8a4a625cd021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31d02b0842461dc42027ffb6aad8ba96d9f721ee3f4d1e60ddf20048dc3e74fa 0.600000000000 1802318 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": 1314677, "vin": [ { "gen": { "height": 1314667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31d02b0842461dc42027ffb6aad8ba96d9f721ee3f4d1e60ddf20048dc3e74fa" } } ], "extra": [ 1, 28, 203, 162, 34, 164, 9, 228, 235, 76, 21, 41, 86, 224, 36, 169, 163, 205, 124, 74, 73, 143, 222, 66, 99, 255, 67, 215, 248, 164, 166, 37, 205, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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