Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f8d75fb4434d24b797b837c6438cdf86515ebcf68ab2f55d8f647fbae68e1b

Tx prefix hash: e8985a45e818180da4c71f919730172c56f97bb3d5a461c9224d83c9c44bc083
Tx public key: 4feb2b6606fa2d13772eb3d290e4e976e4d4543a427962e3b762f16179e8d0a0
Timestamp: 1750896128 Timestamp [UCT]: 2025-06-26 00:02:08 Age [y:d:h:m:s]: 00:193:20:12:47
Block: 1312811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136615 RingCT/type: yes/0
Extra: 014feb2b6606fa2d13772eb3d290e4e976e4d4543a427962e3b762f16179e8d0a00211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db99e0f52d980b54b3b354cd419eab6006274eddc44e1cddceaf584960c472a9 0.600000000000 1800446 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": 1312821, "vin": [ { "gen": { "height": 1312811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db99e0f52d980b54b3b354cd419eab6006274eddc44e1cddceaf584960c472a9" } } ], "extra": [ 1, 79, 235, 43, 102, 6, 250, 45, 19, 119, 46, 179, 210, 144, 228, 233, 118, 228, 212, 84, 58, 66, 121, 98, 227, 183, 98, 241, 97, 121, 232, 208, 160, 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