Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ffeed8881e90bd3eda907f6db401e2baa604c427bdc13f28e928b9c2573f408

Tx prefix hash: 1c1e6ae0799daaa824a2599990c6c0c3644728701ef50daaba4fa271b1cd25b4
Tx public key: dd3714b474fc3474a2c440c14dcd97fbc00a611365c3aa796577f06d2a78b5b9
Timestamp: 1755442541 Timestamp [UCT]: 2025-08-17 14:55:41 Age [y:d:h:m:s]: 00:094:05:44:26
Block: 1348575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67194 RingCT/type: yes/0
Extra: 01dd3714b474fc3474a2c440c14dcd97fbc00a611365c3aa796577f06d2a78b5b90211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c2481f1a5bbb570241b0fcf1b3eb32ec63ebb9e177dd5a25f33ee99f8ef824 0.600000000000 1836502 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": 1348585, "vin": [ { "gen": { "height": 1348575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c2481f1a5bbb570241b0fcf1b3eb32ec63ebb9e177dd5a25f33ee99f8ef824" } } ], "extra": [ 1, 221, 55, 20, 180, 116, 252, 52, 116, 162, 196, 64, 193, 77, 205, 151, 251, 192, 10, 97, 19, 101, 195, 170, 121, 101, 119, 240, 109, 42, 120, 181, 185, 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