Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b68bafcb406fc07c2d28d7db4a9343336f4bc70de0c35a4b535d9f3cb766692e

Tx prefix hash: 028fd2aa7cff69865e09d02d51d8f8390eecad5cced53117e7f6fa8e493d4ad0
Tx public key: 3e69529324a6a2e84389834d386b001105d7118e9393b39e0727c2fc64f3ab52
Timestamp: 1750528282 Timestamp [UCT]: 2025-06-21 17:51:22 Age [y:d:h:m:s]: 00:220:12:54:12
Block: 1309919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155375 RingCT/type: yes/0
Extra: 013e69529324a6a2e84389834d386b001105d7118e9393b39e0727c2fc64f3ab520211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af1a441bb843d2ecd7e6e5fcdd30b8b7776f57bd2eab3469d8a4ea81dcbd606a 0.600000000000 1797536 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": 1309929, "vin": [ { "gen": { "height": 1309919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af1a441bb843d2ecd7e6e5fcdd30b8b7776f57bd2eab3469d8a4ea81dcbd606a" } } ], "extra": [ 1, 62, 105, 82, 147, 36, 166, 162, 232, 67, 137, 131, 77, 56, 107, 0, 17, 5, 215, 17, 142, 147, 147, 179, 158, 7, 39, 194, 252, 100, 243, 171, 82, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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