Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ec096717f72c62eb37fb4f1cb661f1a983cd41682985f17e74bf0bac4ec7197

Tx prefix hash: 95498ce60716146cca3f00caafae3f4dea6a8ae951491872a2848c6370a7f008
Tx public key: 3f98ee43db80a49e7a8643b4d37fa100f6ed28b589dd363fb7bc9cdd96c9e28a
Timestamp: 1758126701 Timestamp [UCT]: 2025-09-17 16:31:41 Age [y:d:h:m:s]: 00:097:05:50:30
Block: 1370530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69625 RingCT/type: yes/0
Extra: 013f98ee43db80a49e7a8643b4d37fa100f6ed28b589dd363fb7bc9cdd96c9e28a021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d13682f3d4e685e00b2ff63c5ac50b04a2dc52e346c5e7a0e688385fdcd7cdd6 0.600000000000 1858607 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": 1370540, "vin": [ { "gen": { "height": 1370530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d13682f3d4e685e00b2ff63c5ac50b04a2dc52e346c5e7a0e688385fdcd7cdd6" } } ], "extra": [ 1, 63, 152, 238, 67, 219, 128, 164, 158, 122, 134, 67, 180, 211, 127, 161, 0, 246, 237, 40, 181, 137, 221, 54, 63, 183, 188, 156, 221, 150, 201, 226, 138, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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