Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f1944d882c9fa7fdd2575cf7d629cc8b2c51112b06a9c12a1c74e36afa4096

Tx prefix hash: f5073fd1bfd4ffd7ac788d9d28e5edde6f1eb4e2a02740a794eb3e88e96f08fb
Tx public key: 85f40969ade5575ba8df7df1ca17f467b54965c10ca032bdb049f463f72905be
Timestamp: 1756736986 Timestamp [UCT]: 2025-09-01 14:29:46 Age [y:d:h:m:s]: 00:131:02:22:58
Block: 1359137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93760 RingCT/type: yes/0
Extra: 0185f40969ade5575ba8df7df1ca17f467b54965c10ca032bdb049f463f72905be021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdb703660459559207d1fbf1ff7f3caa26a7c6b40b0487fe02c85f1d60fb313c 0.600000000000 1847150 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": 1359147, "vin": [ { "gen": { "height": 1359137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdb703660459559207d1fbf1ff7f3caa26a7c6b40b0487fe02c85f1d60fb313c" } } ], "extra": [ 1, 133, 244, 9, 105, 173, 229, 87, 91, 168, 223, 125, 241, 202, 23, 244, 103, 181, 73, 101, 193, 12, 160, 50, 189, 176, 73, 244, 99, 247, 41, 5, 190, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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